> We're only mapping authentication errors at this point (error code 49). Is
> there a standard for the sub codes (i.e. Account Locked, etc.?).
I'm not aware of any such standard, so I asked the LDAP folks in my
group about this. Our OpenLDAP guru had this to say:
My only exposure to Accou
We're only mapping authentication errors at this point (error code 49). Is
there a standard for the sub codes (i.e. Account Locked, etc.?). That is
what is currently mapped in the AD specific file.
On Thu, Dec 30, 2010 at 8:24 AM, Marvin Addison wrote:
> > I've written some code for CAS4 to m
> I've written some code for CAS4 to map the LDAP error codes to Java General
> Security Exceptions
> I've got a simple implementation for Microsoft AD because someone had given
> me the error mappings in a previous JIRA issue.
In my experience the Microsoft LDAP error codes are compliant to t
I've written some code for CAS4 to map the LDAP error codes to Java General
Security Exceptions. The code isn't completely done, but its relatively
stable:
https://source.jasig.org/cas3/trunk/cas-server-support-ldap/src/main/java/org/jasig/cas/server/authentication/
I've got a simple implementat
