-
Notifications
You must be signed in to change notification settings - Fork 84
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
add: User identity negotiation #402
add: User identity negotiation #402
Conversation
Hello! Thank you for the pull request! It is great to see an initiative towards the integration on authorization mechanisms in DICOM-rs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @nicholasrussel! I am adding this contribution as a candidate for DICOM-rs 0.7.0, but we may need a reiteration of the code first. Please see the suggestions inline, and let me know your availability to work on this.
If you also have any ideas for testing the changes in a real scenario, I would be grateful to know. The PACS archives I usually work with do not feature user identity negotiation.
- Remove `Unsupported` - rename SAMLAssertion to `SamlAssertion` - rename JWT to `Jwt` - make UserIdentityType non-exhaustive
1591a42
to
8057259
Compare
- constrain to at most one user identity negotiation variable set
- declare conflict with other user identity forms - + format code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Despite there being gaps in the ecosystem for full authentication support, there is interest in expanding the ul
crate with the knowledge of user identity parts, plus the extra of making these available in the dicom-storescu
tool. This appears to be in order, so I will merge it onto the 0.7 milestone. Much appreciated! 👍
Hello,
Looking for your feedback in adding some of the user identity negotiation options.
In order to keep this minimal, I added the entrypoint into retrieving this data into the existing AccessControl trait. The downside being that it breaks the interface.
Thanks