You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Aman Nanner (JIRA)" <ji...@apache.org> on 2006/09/21 18:58:22 UTC
[jira] Created: (DIRSERVER-747) Creating new custom Authenticator
requires it being in the same package as LdapPrincipal
Creating new custom Authenticator requires it being in the same package as LdapPrincipal
----------------------------------------------------------------------------------------
Key: DIRSERVER-747
URL: http://issues.apache.org/jira/browse/DIRSERVER-747
Project: Directory ApacheDS
Issue Type: Improvement
Components: core
Affects Versions: 1.0-RC4
Reporter: Aman Nanner
Priority: Minor
I have created a new custom authenticator that subclasses AbstractAuthenticator, but I have discovered that it must belong in the same package as org.apache.directory.server.core.authn.LdapPrincipal, because it creates a new instance of LdapPrincipal, but the constructor of LdapPrincipal only has package-level access. This itself isn't a huge deal, but the custom authenticator must also be loaded by the same class loader that loads LdapPrincipal, or else it is not considered to belong to the same package (even though it shares the package name). This causes some deployment issues on our J2EE server. This can also be worked around, but it's kind of a pain. If one of the features of ApacheDS is custom authenticators, then I think this issue should be resolved in some fashion such that custom authenticators can reside in a different package.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (DIRSERVER-747) Creating new custom Authenticator
requires it being in the same package as LdapPrincipal
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu reassigned DIRSERVER-747:
---------------------------------------
Assignee: Alex Karasulu
> Creating new custom Authenticator requires it being in the same package as LdapPrincipal
> ----------------------------------------------------------------------------------------
>
> Key: DIRSERVER-747
> URL: https://issues.apache.org/jira/browse/DIRSERVER-747
> Project: Directory ApacheDS
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.0-RC4
> Reporter: Aman Nanner
> Assignee: Alex Karasulu
> Priority: Minor
> Fix For: 1.5.4
>
>
> I have created a new custom authenticator that subclasses AbstractAuthenticator, but I have discovered that it must belong in the same package as org.apache.directory.server.core.authn.LdapPrincipal, because it creates a new instance of LdapPrincipal, but the constructor of LdapPrincipal only has package-level access. This itself isn't a huge deal, but the custom authenticator must also be loaded by the same class loader that loads LdapPrincipal, or else it is not considered to belong to the same package (even though it shares the package name). This causes some deployment issues on our J2EE server. This can also be worked around, but it's kind of a pain. If one of the features of ApacheDS is custom authenticators, then I think this issue should be resolved in some fashion such that custom authenticators can reside in a different package.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRSERVER-747) Creating new custom Authenticator
requires it being in the same package as LdapPrincipal
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu closed DIRSERVER-747.
-----------------------------------
Resolution: Fixed
Yep this should not long be an issue - as Emmanuel pointed out it was fixed as part of the BB refactoring.
> Creating new custom Authenticator requires it being in the same package as LdapPrincipal
> ----------------------------------------------------------------------------------------
>
> Key: DIRSERVER-747
> URL: https://issues.apache.org/jira/browse/DIRSERVER-747
> Project: Directory ApacheDS
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.0-RC4
> Reporter: Aman Nanner
> Assignee: Alex Karasulu
> Priority: Minor
> Fix For: 1.5.4
>
>
> I have created a new custom authenticator that subclasses AbstractAuthenticator, but I have discovered that it must belong in the same package as org.apache.directory.server.core.authn.LdapPrincipal, because it creates a new instance of LdapPrincipal, but the constructor of LdapPrincipal only has package-level access. This itself isn't a huge deal, but the custom authenticator must also be loaded by the same class loader that loads LdapPrincipal, or else it is not considered to belong to the same package (even though it shares the package name). This causes some deployment issues on our J2EE server. This can also be worked around, but it's kind of a pain. If one of the features of ApacheDS is custom authenticators, then I think this issue should be resolved in some fashion such that custom authenticators can reside in a different package.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-747) Creating new custom Authenticator
requires it being in the same package as LdapPrincipal
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-747:
----------------------------------------
Fix Version/s: 1.5.4
This should be fixed in 1.5.4
> Creating new custom Authenticator requires it being in the same package as LdapPrincipal
> ----------------------------------------------------------------------------------------
>
> Key: DIRSERVER-747
> URL: https://issues.apache.org/jira/browse/DIRSERVER-747
> Project: Directory ApacheDS
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.0-RC4
> Reporter: Aman Nanner
> Priority: Minor
> Fix For: 1.5.4
>
>
> I have created a new custom authenticator that subclasses AbstractAuthenticator, but I have discovered that it must belong in the same package as org.apache.directory.server.core.authn.LdapPrincipal, because it creates a new instance of LdapPrincipal, but the constructor of LdapPrincipal only has package-level access. This itself isn't a huge deal, but the custom authenticator must also be loaded by the same class loader that loads LdapPrincipal, or else it is not considered to belong to the same package (even though it shares the package name). This causes some deployment issues on our J2EE server. This can also be worked around, but it's kind of a pain. If one of the features of ApacheDS is custom authenticators, then I think this issue should be resolved in some fashion such that custom authenticators can reside in a different package.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-747) Creating new custom Authenticator
requires it being in the same package as LdapPrincipal
Posted by "Martin Alderson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491636 ]
Martin Alderson commented on DIRSERVER-747:
-------------------------------------------
In 1.5 (at least) you can create an instance of LdapPrincipal using the createLdapPrincipal method provided by your authenticators base class - AbstractAuthenticator.
> Creating new custom Authenticator requires it being in the same package as LdapPrincipal
> ----------------------------------------------------------------------------------------
>
> Key: DIRSERVER-747
> URL: https://issues.apache.org/jira/browse/DIRSERVER-747
> Project: Directory ApacheDS
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.0-RC4
> Reporter: Aman Nanner
> Priority: Minor
>
> I have created a new custom authenticator that subclasses AbstractAuthenticator, but I have discovered that it must belong in the same package as org.apache.directory.server.core.authn.LdapPrincipal, because it creates a new instance of LdapPrincipal, but the constructor of LdapPrincipal only has package-level access. This itself isn't a huge deal, but the custom authenticator must also be loaded by the same class loader that loads LdapPrincipal, or else it is not considered to belong to the same package (even though it shares the package name). This causes some deployment issues on our J2EE server. This can also be worked around, but it's kind of a pain. If one of the features of ApacheDS is custom authenticators, then I think this issue should be resolved in some fashion such that custom authenticators can reside in a different package.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.