-
Notifications
You must be signed in to change notification settings - Fork 827
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
Shadow Users are not getting updated after user logs out and login again #2917
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/187740654 The labels on this github issue will be updated when the story is started. |
I assume you mean you set in yml: And the roles from your IdP has be changed. Will verify and if yes, then we have bug, yes. @Tallicia FYI |
So here when certain groups are assigned to the user in idp , they get reflected in the shadow user but when certain memberships are deleted then even though the access token coming from the idp has updatd set of groups(like not having the ones that are being removed ) is not deleting the groups (that are no more valid ) in the shadow user |
I can confirm this issue. @peterhaochen47 FYI I configured in uaa.yml `
` Then on my IdP I set certain groups for the user, e.g. group1, group2 And in oauth-client supported group1, group2, group3, etc. With login to UAA (and proxy to IdP) , requested scope"group1 group2" I received a new Shadow user with and scope assignment of ["group1", "group2"]. After logout and login in UAA (and ext. IdP) and removal of group2 in IdP I started login again. Result still is: ["group1", "group2"] If I perform steps like : -> Reason is, that for existing shadow user, this method is executed If a GroupMemberShip entry is done with the wrong origin, then this assignment is not removed and stays. |
Test shows: SAML OK OIDC we have an issue
SECURITY NOTICE: If you have found a security problem in the UAA, please do not file a public github issue. Instead, please send an email to security@cloudfoundry.org
Thanks for taking the time to file an issue. You'll minimize back and forth and help us help you more effectively by answering all of the following questions as specifically and completely as you can.
What version of UAA are you running?
What output do you see from
curl <YOUR_UAA>/info -H'Accept: application/json'
?How are you deploying the UAA?
77.10.0
Problem Statement
Today when 2 uaa are used federating with each other the shadow users that gets created is not getting updated with new set of permissions coming from access_token from the other uaa counterpart.
So what we see is shadow user , gets updated with new permissions when user authenticates but it does not remove the permissions that has been removed .
My user journey is like this
Typically roles that are removed are not removed but roles that are added can be seen
The text was updated successfully, but these errors were encountered: