Skip to content
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.

Sign up for GitHub

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

Jump to bottom

automount sssd issue when 2 automount maps have the same key (one un uppercase, one in lowercase) #5330

Closed
pbrezina opened this issue Sep 23, 2020 · 1 comment
Closed

automount sssd issue when 2 automount maps have the same key (one un uppercase, one in lowercase) #5330

pbrezina opened this issue Sep 23, 2020 · 1 comment
Assignees
@pbrezina
Labels
Closed: Fixed Issue was closed as fixed.

Comments

@pbrezina
Copy link
Member

pbrezina commented Sep 23, 2020 •
edited by alexey-tikhonov
Loading

There can be more entries with same cn attribute value that differs only in casing if different attribute is chosen as rdn. SSSD then searches for (cn=name)when name folder is being mounted but this returns both lowercase and uppercase entry and we only store one (which may not be the desired one based on the order in the result) and fail to mount one of the directories.

dn: automountinformation=volume1,ou=auto.home,dc=example,dc=com
automountInformation: volume1
cn: NAME
objectClass: top
objectClass: automount

dn: automountinformation=volume2,ou=auto.home,dc=example,dc=com
automountInformation: volume2
cn: name
objectClass: top
objectClass: automount

RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1873715
@pbrezina pbrezina self-assigned this Sep 23, 2020
pbrezina added a commit to pbrezina/sssd that referenced this issue Sep 23, 2020
@pbrezina
autofs: if more then one entry is found store all of them
bf6df8a 
There can be more entries with same cn (automountKey) attribute value
that differs only in casing if different attribute is chosen as rdn.
SSSD then searches for (cn=name)when name folder is being mounted but
this returns both lowercase and uppercase entry and we only store one
(which may not be the desired one based on the order in the result)
and fail to mount one of the directories.

Resolves:
SSSD#5330
@pbrezina pbrezina mentioned this issue Sep 23, 2020
Closed
pbrezina added a commit to pbrezina/sssd that referenced this issue Sep 29, 2020
@pbrezina
autofs: if more then one entry is found store all of them
7cec495 
There can be more entries with same cn (automountKey) attribute value
that differs only in casing if different attribute is chosen as rdn.
SSSD then searches for (cn=name)when name folder is being mounted but
this returns both lowercase and uppercase entry and we only store one
(which may not be the desired one based on the order in the result)
and fail to mount one of the directories.

Resolves:
SSSD#5330
@pbrezina
Copy link
Member Author

pbrezina commented Oct 6, 2020

Pushed PR: #5331

  • master
    • 93e35c7 - autofs: if more then one entry is found store all of them

@pbrezina pbrezina added the Closed: Fixed Issue was closed as fixed. label Oct 6, 2020
pbrezina pushed a commit that referenced this issue May 10, 2021
@pbrezina
Tests: automount sssd issue when 2 automount maps have the same key (…
47b40cc 
…one un uppercase, one in lowercase)

With 2 automount entries in LDAP with same key ( cn: MIT and cn: mit),
autofs only works for one of them ( the one in uppercase )

Verifies: #5330

Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1873715

Reviewed-by: Steeve Goveas <sgoveas@redhat.com>
akuster pushed a commit to akuster/sssd that referenced this issue May 18, 2021
@akuster
Tests: automount sssd issue when 2 automount maps have the same key (…
bf3c25d 
…one un uppercase, one in lowercase)

With 2 automount entries in LDAP with same key ( cn: MIT and cn: mit),
autofs only works for one of them ( the one in uppercase )

Verifies: SSSD#5330

Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1873715

Reviewed-by: Steeve Goveas <sgoveas@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pbrezina pbrezina

Labels
Closed: Fixed Issue was closed as fixed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pbrezina