After logging into Copr using OpenID, Copr reads list of user's groups from the openid response. I'm curious if there's some caching or DB synchronization in the background. @psss created a new group "temtee" but we failed to get the group in OpenID response.
Yes, I tried to log out and log in several times the newly added group was still not there. I had to open a new private window to get the password prompt and then the new group appeared.
I suppose we should document this as a known thing in https://docs.pagure.org/copr.copr/user_documentation.html#how-can-i-create-new-group ?
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
So, there would be a cache... the sssd that ipsilon (id.fedoraproject.org) uses.
I am not sure what the value is there, but I think it caches for some time.
Logging out and back on again should cause it to requery right away however.
You can go to: https://id.fedoraproject.org/logout to logout and then any normal place to login again?
I just deleted the temtee group and added teamtee... so you can try it out with this?
Ah, that could help indeed. Copr isn't doing this by default, it just drops the session. https://github.com/fedora-copr/copr/blob/739a509b38b068ddf64861155675263e1bf44770/frontend/coprs_frontend/coprs/auth.py#L147-L151
Ah, sorry, I missed your comment and already added the group. But I can confirm that clicking on the logout url above got me to the copr password page.
ok. Anything more to do here then? just document on your side to wait or logout?
@praiskup, what about adding the logout link directly to the group page? You already have a warning there so that would make it even more straightforward.
Maybe, or meybe we could just document the link in our documentation.
Metadata Update from @praiskup: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.