-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Unable to change the domain when a user is authenticated by SAML #10003
Comments
this seems to be regression of security bug fixes in there are two related fixes |
Thanks @weizhouapache Saml authenticatied users can change the domain till the 4.18.2.3 release. The issue is occurring from the 4.18.2.4 release |
@kiranchavala can you change global setting |
@weizhouapache Getting the same error even after changing the |
@weizhouapache @kiranchavala , I set this to 4.20.1 but am having second thoughts. should (and can!) we move this forward or is it too complicated to solve? |
@DaanHoogland @kiranchavala |
Currently, there is no option to select a specific domain to during login for saml Once logged in user's get the option to switch to a specific domain |
thanks @kiranchavala |
clear, thanks @weizhouapache @kiranchavala |
I will have a look @DaanHoogland @kiranchavala |
fixed by #10047 |
ISSUE TYPE
BUG
COMPONENT NAME
Component: Bug
CLOUDSTACK VERSION
Cloudstack version 4.18.2.5, 4.19.1.3
SUMMARY
Unable to change the domain when a user is authenticated by SAML
Steps to reproduce the issue
On 4.19.1.3 environment
Video recording
https://www.loom.com/share/7dd809008a7649e7907bdf10c56af185?sid=86038cae-f441-4d8f-b76a-0db59486bf0b
Followed, the same steps on 4.18.1.1 and found no issue on 4.18.1.1
Video recording
https://www.loom.com/share/6cc8b0625c324976b338965ae679ae26?sid=01b0d96e-5b6d-4d77-bacd-e81c62e66610
Expected Behaviour
Cloudstack saml configured users should be able to change the domain
Actual Behaviour
Cloudstack saml configured users are not able to change the domain
The text was updated successfully, but these errors were encountered: