-
Notifications
You must be signed in to change notification settings - Fork 20
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
Allow to request specific properties when logging in #148
Comments
Hi, I would like to contribute to this issue, can you assign to me? |
With pleasure :-) I'll try to extend a bit the description to make it more descriptive and precise too. Thanks a lot |
Btw @Dominik26-1 , can you tell me who you are and how you're connected to DIRAC/Rucio ? (mail is fine) |
Hi,
I am student from technical university of Kosice and we have to contribute
to one open issue. I study IT, programming and also I am full time Java
developer in work.
Dominik
Dňa ut 17. 10. 2023, 10:36 chaen ***@***.***> napísal(a):
… Btw @Dominik26-1 <https://github.com/Dominik26-1> , can you tell me who
you are and how you're connected to DIRAC/Rucio ? (mail is fine)
—
Reply to this email directly, view it on GitHub
<#148 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATYF5FYLROIYPT4EIL4ZBSLX7Y7P5AVCNFSM6AAAAAA6BS72NCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRVHEZTSMRSGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Ah ok ! We were planning on giving this task at a workshop tomorrow. If you are happy with this, I will assign you a less time critical one by the end of the week. Looking forward to your contribution 😃 |
" Ah ok ! We were planning on giving this task at a workshop tomorrow. If
you are happy with this, I will assign you a less time critical one by the
end of the week. Looking forward to your contribution 😃
—
Hi,
I am okay with that. But we have to put the link on issue till tomorrow
afternoon.
If you have something not trivia in your mind and as a first good issue as
well, I will very appreciate it to have at least something to assign on me
soon.
Thanks
Dominik
|
Currently, running
dirac login <vo> --property <propA> --property <propB>
works in the sense that it does not trow an error, but it still only returns the properties mapped to the group.The requested properties are correctly stored in the
AuthDB
, but not exploited when generated requests.It needs to be added here
diracx/src/diracx/routers/auth.py
Line 279 in d63cde8
The text was updated successfully, but these errors were encountered: