| Summary: | ldap user cannot authenticate | ||
|---|---|---|---|
| Product: | Red Hat Storage Console | Reporter: | Martin Kudlej <mkudlej> |
| Component: | core | Assignee: | Timothy Asir <tjeyasin> |
| core sub component: | authentication | QA Contact: | sds-qe-bugs |
| Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | khartsoe, mkudlej, nthomas, sankarshan |
| Version: | 2 | ||
| Target Milestone: | --- | ||
| Target Release: | 2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-11-19 05:33:00 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: | |
|
Description
Martin Kudlej
2016-01-21 13:13:01 UTC
This is not a bug. By design and based on the grooming/UX discussions, user must be imported to USM. If the user is not imported, USM treat the user as invalid and will not continue with login. So according to my expectation an external LDAP could potentially have 1000's of users. Obviously only a small subset would need to log into USM. Is the term "import" meant to allow this type of access? i.e. although the authentication is delegated to the ldap system, the "import" allows that person access to USM? If so then I would say this bug is invalid, but the use of the word "import" might be confusing to some users. Perhaps this is only a documentation issue. That is right Jeff. Import means adding a subset of users who can access USM from LDAP User import tested with rhscon-core-0.0.29-1.el7scon.x86_64 rhscon-ui-0.0.43-1.el7scon.noarch and it works. --> Verified I agree that current implementation is more logical than fuzzy Requirement. |