Anything that could be done to prioritize getting Jira implemented would be appreciated.
I see it was recently moved to unassigned and not in a sprint.
Anything that could be done to prioritize getting Jira implemented would be appreciated.
I see it was recently moved to unassigned and not in a sprint.
FWIW, based on the test just done, I believe the problem is CAUSED by having to login again, not solved by it.
Usual case
This particular case
Hi,
Are you saying you have a user you can reliably reproduce this with?
Thx,
Ann
Now that we have isolated the problem, all users can reproduce this. It happens when the user has to re-authenticate.
The problem seems to be in this code:
o.s.s.a.UserRegistrarImpl is trying to check if the authentication provider results includes the same groups for the user as are currently in the system (as done by the previous background sync). This code is checking for direct membership and not checking for transitive member (because the user is in group CHILD_GROUP and group CHILD_GROUP is in group PARENT_GROUP), so it removes the user from 3 groups.
My conclusion is a guess, i do not have access to the source code. The log lines supporting my guess are:
2025.09.18 13:55:38 DEBUG web[47e4017e-0d86-4d55-a1e6-2ead3a6c642a][o.s.s.a.UserRegistrarImpl] List of groups returned by the identity provider âCHILD_GROUPâ
2025.09.18 13:55:38 TRACE web[47e4017e-0d86-4d55-a1e6-2ead3a6c642a][sql] time=0ms | sql=select g.uuid as uuid, g.name as name, g.description as description, g.created_at as âcreatedAtâ, g.updated_at as âupdatedAtâ from groups g where g.name in ( ? , ? , ? , ? ) | params=sonar-users, sunbirddcim//all-organization-members, PARENT_GROUP, GRAND_PARENT_GROUP
2025.09.18 13:55:38 TRACE web[47e4017e-0d86-4d55-a1e6-2ead3a6c642a][sql] time=0ms | sql=select g.uuid as uuid, g.name as name, g.description as description, g.created_at as âcreatedAtâ, g.updated_at as âupdatedAtâ from groups g where g.name = ? | params=sonar-users
2025.09.18 13:55:38 DEBUG web[47e4017e-0d86-4d55-a1e6-2ead3a6c642a][o.s.s.a.UserRegistrarImpl] Removing group âsunbirddcim//all-organization-membersâ from user âfooâ
2025.09.18 13:55:38 TRACE web[47e4017e-0d86-4d55-a1e6-2ead3a6c642a][sql] time=0ms | sql=delete from groups_users where user_uuid = ? and group_uuid = ? | params=AYPNacXETpblgMn6FlY3, AYsLFEBjtL-FLoUNThv_
2025.09.18 13:55:38 DEBUG web[47e4017e-0d86-4d55-a1e6-2ead3a6c642a][o.s.s.a.UserRegistrarImpl] Removing group âGRAND_PARENT_GROUPâ from user âfooâ
2025.09.18 13:55:38 TRACE web[47e4017e-0d86-4d55-a1e6-2ead3a6c642a][sql] time=1ms | sql=delete from groups_users where user_uuid = ? and group_uuid = ? | params=AYPNacXETpblgMn6FlY3, AYsLFEBKtL-FLoUNThvj
2025.09.18 13:55:38 DEBUG web[47e4017e-0d86-4d55-a1e6-2ead3a6c642a][o.s.s.a.UserRegistrarImpl] Removing group âPARENT_GROUPâ from user âfooâ
Hi,
Thanks for narrowing this down. Itâs very helpful. This has been re-flagged for the team.
Thx,
Ann
Hi @andrew-garland,
Thank you for your patience and for all your investigations efforts.
We believe this is related to Team membership lost on login when GitHub auto-provisioning enabled. (nice catch
@Colin ).
I added it to our next sprint!
Thanks
Thanks for the update. Hopefully, this time it stays in the sprint, since that issue was previously in sprints Identity-25Q3-3 and Identity-25Q3-2
Any update on getting this implemented?
Hi,
FYI, this is currently slated to be fixed in v2026.2 ![]()
Iâm advocating for an earlier fix, but Iâm not holding my breath.
Ann