You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Douglas Britsch (JIRA)" <ji...@apache.org> on 2010/07/19 19:23:51 UTC
[jira] Created: (SLING-1606) Please expose and
org.apache.jackrabbit.core.security.* to allow overriding of UserManager
interface and use of Authentication
Please expose and org.apache.jackrabbit.core.security.* to allow overriding of UserManager interface and use of Authentication
------------------------------------------------------------------------------------------------------------------------------
Key: SLING-1606
URL: https://issues.apache.org/jira/browse/SLING-1606
Project: Sling
Issue Type: Improvement
Components: API
Affects Versions: JCR Jackrabbit Server 2.0.6
Environment: Felix
Reporter: Douglas Britsch
I need to replace the UserManager impl in jackrabbit to allow an external authentication provider outside of the JCR repo. I can make it work for authentication with the AUthenticationHandler and LoginModulePlugin interfaces provided through sling, but must override the UserManager because my usecase does not allow the users to exist in the repository.
The current bundle exports the org.apache.jackrabbit.core.security.principal package, but the UserManagerImpl is in the org.apache.jackrabbit.core.security.user package and I also need authentication which is in the org.apache.jackrabbit.core.security.authentication package. Any reason you cannot/don't want to export these packages. It would be helpful as they are needed to use jackrabbits extension model.
Simply adding the following to the Export-Package section of the jackrabbit-server pom.xml allows my case to work:
org.apache.jackrabbit.core.security.*;version=2.0.0,
org.apache.jackrabbit.core.*;version=2.0.0
Thanks!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1606) Please expose and
org.apache.jackrabbit.core.security.* to allow overriding of UserManager
interface and use of Authentication
Posted by "Douglas Britsch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Douglas Britsch resolved SLING-1606.
------------------------------------
Resolution: Not A Problem
Thanks, will do that, and hope for an eventual package redesign in jackrabbit :-)
> Please expose and org.apache.jackrabbit.core.security.* to allow overriding of UserManager interface and use of Authentication
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-1606
> URL: https://issues.apache.org/jira/browse/SLING-1606
> Project: Sling
> Issue Type: Improvement
> Components: API
> Affects Versions: JCR Jackrabbit Server 2.0.6
> Environment: Felix
> Reporter: Douglas Britsch
>
> I need to replace the UserManager impl in jackrabbit to allow an external authentication provider outside of the JCR repo. I can make it work for authentication with the AUthenticationHandler and LoginModulePlugin interfaces provided through sling, but must override the UserManager because my usecase does not allow the users to exist in the repository.
> The current bundle exports the org.apache.jackrabbit.core.security.principal package, but the UserManagerImpl is in the org.apache.jackrabbit.core.security.user package and I also need authentication which is in the org.apache.jackrabbit.core.security.authentication package. Any reason you cannot/don't want to export these packages. It would be helpful as they are needed to use jackrabbits extension model.
> Simply adding the following to the Export-Package section of the jackrabbit-server pom.xml allows my case to work:
> org.apache.jackrabbit.core.security.*;version=2.0.0,
> org.apache.jackrabbit.core.*;version=2.0.0
> Thanks!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1606) Please expose and
org.apache.jackrabbit.core.security.* to allow overriding of UserManager
interface and use of Authentication
Posted by "Douglas Britsch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Douglas Britsch closed SLING-1606.
----------------------------------
> Please expose and org.apache.jackrabbit.core.security.* to allow overriding of UserManager interface and use of Authentication
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-1606
> URL: https://issues.apache.org/jira/browse/SLING-1606
> Project: Sling
> Issue Type: Improvement
> Components: API
> Affects Versions: JCR Jackrabbit Server 2.0.6
> Environment: Felix
> Reporter: Douglas Britsch
>
> I need to replace the UserManager impl in jackrabbit to allow an external authentication provider outside of the JCR repo. I can make it work for authentication with the AUthenticationHandler and LoginModulePlugin interfaces provided through sling, but must override the UserManager because my usecase does not allow the users to exist in the repository.
> The current bundle exports the org.apache.jackrabbit.core.security.principal package, but the UserManagerImpl is in the org.apache.jackrabbit.core.security.user package and I also need authentication which is in the org.apache.jackrabbit.core.security.authentication package. Any reason you cannot/don't want to export these packages. It would be helpful as they are needed to use jackrabbits extension model.
> Simply adding the following to the Export-Package section of the jackrabbit-server pom.xml allows my case to work:
> org.apache.jackrabbit.core.security.*;version=2.0.0,
> org.apache.jackrabbit.core.*;version=2.0.0
> Thanks!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1606) Please expose and
org.apache.jackrabbit.core.security.* to allow overriding of UserManager
interface and use of Authentication
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889948#action_12889948 ]
Felix Meschberger commented on SLING-1606:
------------------------------------------
I am against exposing any of the o.a.j.core packages. The problem is, that these packages do not expose proper API, leak internals and are not properly separated from other packages (and yes, this is a known but hard to solve issue).
I suggest you create a fragment bundle, which you attach to the Embedded Jackrabbit Server bundle. Like this you have full access to the complete Jackrabbit core library contents from your UserManager and can easily configure your UserManager in the repository.xml file to be used by Jackrabbit.
> Please expose and org.apache.jackrabbit.core.security.* to allow overriding of UserManager interface and use of Authentication
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-1606
> URL: https://issues.apache.org/jira/browse/SLING-1606
> Project: Sling
> Issue Type: Improvement
> Components: API
> Affects Versions: JCR Jackrabbit Server 2.0.6
> Environment: Felix
> Reporter: Douglas Britsch
>
> I need to replace the UserManager impl in jackrabbit to allow an external authentication provider outside of the JCR repo. I can make it work for authentication with the AUthenticationHandler and LoginModulePlugin interfaces provided through sling, but must override the UserManager because my usecase does not allow the users to exist in the repository.
> The current bundle exports the org.apache.jackrabbit.core.security.principal package, but the UserManagerImpl is in the org.apache.jackrabbit.core.security.user package and I also need authentication which is in the org.apache.jackrabbit.core.security.authentication package. Any reason you cannot/don't want to export these packages. It would be helpful as they are needed to use jackrabbits extension model.
> Simply adding the following to the Export-Package section of the jackrabbit-server pom.xml allows my case to work:
> org.apache.jackrabbit.core.security.*;version=2.0.0,
> org.apache.jackrabbit.core.*;version=2.0.0
> Thanks!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.