-
Notifications
You must be signed in to change notification settings - Fork 28
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
Question about 5.1.0 release announcement #568
Comments
Hi Dave, sorry for the delayed response (vacation+conference). The mentioned announcement was my first try to solve your problem from #553. However, as it did not solve the problem, I then added the I just checked the code again and realized that I had a bug in the first implementation; so it couldn't work. Now it should update the scope values on a fresh The prerel version is available at https://repo.data.kit.edu/prerel/centos/7/ (and similar). If this is the case this might lead to problems on reauthenticate in your case. |
I am assuming it is version oidc-agent-5.1.1~pr2-1. Let me know if that is not correct. |
Indeed that replaced the "scope" list in the account info that printed with |
I implemented an approach with separate scope lists. It should shortly be available in the devel repo: |
What version? The newest one I see there now is 5.1.0. Did you mean prerel? The newest version there is 5.1.1~pr2, which is the one I tested last week. The Codebase CI failed on the commit added yesterday so maybe that's why there's no new version. |
Yes there currently is a problem with another part of the CI that's why the packages are not pushed to the repo. |
Yes, that works for me without any errors, and without losing track of the initial scopes. Thanks! |
FWIW: Pipelines are back working. |
I have verified that 5.1.0 works with the
oidc-add --skip-check
option added as a result of the problem I reported in #553. However I am confused by the additional release announcement message:I thought that might fix my problem without adding
--skip-check
or making any other changes to the wrapping tool (osg-token-renewer), but I don't see the change in behavior that is desribed. After reauthenticating,oidc-gen -p
sitll shows the original requested scopes. I'm not saying this is necessarily bad, in fact I worried about what that would mean when reauthenticating, because then I would want it to go back to the original list of scopes. I'm just wonder if the above release announcement is correct.Oh, I didn't try re-generating an account from scratch, only reauthenticating. Is that the difference?
The text was updated successfully, but these errors were encountered: