Bug 1484831
Summary: | oadm groups prune does not find groups when using whitelist | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Bruno Andrade <bandrade> |
Component: | apiserver-auth | Assignee: | Mo <mkhan> |
Status: | CLOSED ERRATA | QA Contact: | Chuan Yu <chuyu> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.4.0 | CC: | aos-bugs, chuyu, hgomes, mkhan, wsun |
Target Milestone: | --- | ||
Target Release: | 3.7.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: The LDAP sync/prune command did not take into account the use of groupUIDNameMapping with a whitelist.
Consequence: The sync/prune command would fail with "group not found" errors because it would query for the wrong group name.
Fix: The command was updated to take groupUIDNameMapping into account when using a whitelist.
Result: The command queries for the correct group name when groupUIDNameMapping and a whitelist are used together.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-11-28 22:08:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bruno Andrade
2017-08-24 11:43:05 UTC
looks like the whitelist needs to run through the mapping transformation if present As a temporary workaround, the customer could create a second whitelist with the mapped values: tc509127group1 tc509127group2 tc509127group3 This would allow for normal use of the prune command. moving to Mo, only because he has a PR almost ready to go, can be moved to others as necessary The PR is merged into 3.7 master. Verified with lastest 3.7 build, search the group correctly and run the prune command withou problems. # openshift version openshift v3.7.0-0.126.4 kubernetes v1.7.0+80709908fd etcd 3.2.1 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:3188 |