[ https://issues.apache.org/jira/brow...action_12491636 ]

Martin Alderson commented on DIRSERVER-747:
-------------------------------------------

In 1.5 (at least) you can create an instance of LdapPrincipal using the crea
teLdapPrincipal method provided by your authenticators base class - Abstract
Authenticator.

> 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, b
ut 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
, b
ut the constructor of LdapPrincipal only has package-level access.  This its
elf isn't a huge deal, but the custom authenticator must also be loaded by t
he same class loader that loads LdapPrincipal, or else it is not considered 
to belong to the same packa
ge (even though it shares the package name).  This causes some deployment is
sues 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 dif
ferent package.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[ Post a follow-up to this message ]