Environment
Novell SecureLogin
NSL v 3.51
NSL v 6.x
SecureLogin installed in LDAP mode
no error if user re-enters name using ldap syntax: cn=test, o=whatever
NSL v 3.51
NSL v 6.x
SecureLogin installed in LDAP mode
no error if user re-enters name using ldap syntax: cn=test, o=whatever
Situation
login with NSL LDAP client fails
LDAP error 34 (illegal name) on user login.
LDAP error 17 (undefined type) when attempting to set preferences in SLManager
LDAP error 34 (illegal name) on user login.
LDAP error 17 (undefined type) when attempting to set preferences in SLManager
Resolution
Re-running the NSL LDAP schema extension resolved the problem in
this case. Run ldapschema.exe from the ...\SecureLogin\Tools
directory.
In another case re-running ldapschema.exe still did not create the ldap mappings, but manually creating the ldap mappings resolved the issue.
In another case re-running ldapschema.exe still did not create the ldap mappings, but manually creating the ldap mappings resolved the issue.
Steps to manually create the ldap mapp