New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[studio] LDAP warning message for missing group "ou" is incorrect #1421

Closed
alhambrav opened this Issue Oct 5, 2017 · 2 comments

Comments

@alhambrav
Member

alhambrav commented Oct 5, 2017

The ou (group) attribute was missing from the subtree and the message in the tomcat log was for a missing sn (surname):

[WARN] 2017-10-04 10:08:08,956 [http-nio-8080-exec-2] [security.DbWithLdapExtensionSecurityProvider] | No LDAP attribute sn found for username cbrunato

Here's my LDIF with the missing ou (group) in the subtree:

dn: cn=Chuck Brunato,ou=Developer,dc=example,dc=com
objectClass: inetOrgPerson
objectClass: organizationalPerson
objectClass: person
objectClass: top
cn: Chuck Brunato
sn: Brunato
description: 19650324000000Z
employeeNumber: 3
givenName: Chuck
mail: chuck@example.com
o: myawesomesite
telephoneNumber: 169-637-3314
telephoneNumber: 907-547-9114
uid: cbrunato
userPassword:: c2VjcmV0

@sumerjabri sumerjabri added this to the Crafter CMS v3.0.2 milestone Oct 5, 2017

@sumerjabri sumerjabri added this to Backlog in Crafter CMS v3.0.x Oct 11, 2017

@dejan-brkic dejan-brkic moved this from Backlog to Test & Validate in Crafter CMS v3.0.x Oct 11, 2017

@dejan-brkic

This comment has been minimized.

Show comment
Hide comment
@dejan-brkic
Member

dejan-brkic commented Oct 11, 2017

Done

@dejan-brkic dejan-brkic assigned alhambrav and unassigned dejan-brkic Oct 11, 2017

@alhambrav

This comment has been minimized.

Show comment
Hide comment
@alhambrav

alhambrav Oct 13, 2017

Member

Verified fixed.

Member

alhambrav commented Oct 13, 2017

Verified fixed.

@alhambrav alhambrav closed this Oct 13, 2017

@alhambrav alhambrav moved this from Test & Validate to Completed in Crafter CMS v3.0.x Oct 13, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment