Using: spring-ldap 1.2
Platform: AIX jdk 1.4.2 against Novell eDIR ldap server (I currently do not know what the version is)
I am using the canLogin() code that has been posted on this forum here.
When an account has been expired I get a javax.naming.OperationNotSupportedException exception.
I was wondering if there isn't a more accurate exception for expired accounts?
If not I was wondering if sping-ldap has such a feature as the core spring framework for mapping SQL errors to an exception hieracy and being able to provide your own error codes in a external mapping file. Or to start with injecting your own mapping strategy.
Using this I would be able to catch the OperationNotSupportedException and parse the error message and determine that this is an account expired error and throw my own AccountExpired exception.
BTW: Novell have their error codes listed here:
FAILED --- User [JCHR0001] account is expired.; nested e
xception is org.springframework.ldap.OperationNotSupportedExce ption: [LDAP: error code 53 - NDS error: log account expired (-220)]; nested exc
eption is javax.naming.OperationNotSupportedException: [LDAP: error code 53 - NDS error: log account expired (-220)]|