August 24, 2016 at 8:22 pm #12733AnonymousInactive
I use OpenAM as IDP with a custom AuthChain configured to use a default LDAP Module.
I have a really weird behaviour because the authentication using my custom chain is not always working. Usually after restarting tomcat service couple of times it works again and after an undefined time it doesn’t work anymore.
Here is the error:
/usr/share/tomcat7/openam/openam/log/amAuthentication.error <== "2016-08-24 20:03:46" "Login Failed|service|demo1Chain" 192.168.0.1 "cn=dsameuser,ou=DSAME Users,dc=controlcenter,dc=lu" "Not Available" "Not Available" LDAP-DEMO1 "Not Available" dc=controlcenter,dc=lu INFO 192.168.0.1 AUTHENTICATION-240
Where this “cn=dsameuser,ou=DSAME Users,dc=controlcenter,dc=lu” comes from ? That’s not my default ldap path.
Thank you!August 24, 2016 at 10:57 pm #12735ssripathyParticipant
About dsameuser “dsameuser (cn=dsameuser,ou=DSAME Users,dc=opensso,dc-java,dc=net) binds to the embedded configuration data store when the OpenSSO SDK performs operations on it that are not linked to a particular user (for example, retrieving service configuration information)”
Base on what I have experienced in the past, this error arises due to issues with module configuration.
You must be logged in to reply to this topic.