Replies: 1 comment
-
Adding @yurem to get his comments. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I had this working with version 1.0.22, but now setting up 1.1.1 attempting to login fails. From both CASA and the regular login screen I get the error "Failed to Authenticate". As far as I can tell, I have configured everything the same way.
Turned on Trace logging, I noticed this:
DEBUG [qtp1260134048-20] 98f60ad4-f1f1-4d5a-a1b3-399d7b777118 [jans.orm.ldap.operation.watch.OperationDurationUtil] (OperationDurationUtil.java:26) - LDAP operation: search, duration: PT0.114363482S, dn: DC=COMPANY,DC=DOMAIN, filter: (&(&(objectClass=jansPerson))(&(&(objectClass=top)(objectClass=jansPerson))(&(sAMAccountName=username)))), scope: SUB, batchOperationWraper: io.jans.orm.ldap.impl.LdapBatchOperationWraper@4c820f9c, start: 0, searchLimit: 100, count: 1, controls: null, attributes: null
It appears to be attempting to authenticate/connect to the LDAP with using the objectClass of jansPerson. But our LDAP should have the filter set to objectClass=person. Is this from the recently added jansPerson attribute from pull request #8183 or is there a place this filter is configured that I could not find?
Beta Was this translation helpful? Give feedback.
All reactions