|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 23/Jul/21 08:30 PM
Updated: 25/Jan/23 07:26 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
11.0.7
|
| Fix Version/s: |
12.0.0
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
If the first time a user logs in is with SSO.
And then SSO is down, the users can't login with a fall back security provider like LDAP.
That is the user doesn't click SSO but enters there username/password.
They can't authenticate to ldaps.
It would be nice to offer an option or try to use a security provider kind of like when a user isn't found,
QB tries all security provider.
Maybe something like:
if user created by SSO and logging in with user/password, try all security providers.
|
|
Description
|
If the first time a user logs in is with SSO.
And then SSO is down, the users can't login with a fall back security provider like LDAP.
That is the user doesn't click SSO but enters there username/password.
They can't authenticate to ldaps.
It would be nice to offer an option or try to use a security provider kind of like when a user isn't found,
QB tries all security provider.
Maybe something like:
if user created by SSO and logging in with user/password, try all security providers. |
Show » |
| No work has yet been logged on this issue.
|
|
Improvement
Resolved
Major
New SSO accounts can't authenticate with a security provider like ldap