directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralf Hauser (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-641) provide a security context to
Date Sat, 01 Jul 2006 07:37:30 GMT
    [ ] 

Ralf Hauser commented on DIRSERVER-641:

I see a test whether the session is secured or not, but I doubt that I can see this in an I use for an authorization or Any hints would be highly appreciated!

What I would like to do is to let request for certain elements such as a CRL through without
requiring bind-auth and SSL whereas all other shall insist on this.

> provide a security context to
> ---------------------------------------------------------------------------------------------------------
>          Key: DIRSERVER-641
>          URL:
>      Project: Directory ApacheDS
>         Type: New Feature

>   Components: core
>     Versions: 1.0-RC3
>  Environment: windows and linux
>     Reporter: Ralf Hauser

> 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
> or extending the ServerContext object correspondingly.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message