[jira] Updated: (DIRSERVER-641) provide a security context to org.apache.directory.server.core.authn.AbstractAuthenticator.authenticate()

["Alex Karasulu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DIRSERVER-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Karasulu updated DIRSERVER-641:
------------------------------------

    Fix Version/s:     (was: 1.5.4)
                   1.5.6

> provide a security context to org.apache.directory.server.core.authn.AbstractAuthenticator.authenticate()
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-641
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-641
>             Project: Directory ApacheDS
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: 1.0-RC3
>         Environment: windows and linux
>            Reporter: Ralf Hauser
>             Fix For: 1.5.6
>
>
> The ldap application we are working on has high security requirements, both in terms of "fine-grained"-policies we need to be able to implement as well as for the audit trail we must be able to provide.
> For that, we should be able to distinguish/ensure/record in our authenticate() method
> - whether the bind request was received unprotected or protected
> - if with SSL protected, what session key was negotiated (if with 256+bit AES, client is entitled to see more than with 128 bit, let alone 40). 
> These give our application strong hints whether we must consider a credential (passwords in particular) compromised or not.
> I assume this would either imply adding 1-2 more parameters to the method interface of
>         LdapPrincipal org.apache.directory.server.core.authn.AbstractAuthenticator.authenticate(ServerContext ctx) 
> or extending the ServerContext object correspondingly.

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