[JIRA] (IDP-2003) Support generating a NameID to put into the Subject in the AuthnRequest it issues

Scott Cantor (Jira) jira at shibboleth.atlassian.net
Tue Sep 6 18:04:05 UTC 2022


Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) *commented* on IDP-2003 ( https://shibboleth.atlassian.net/browse/IDP-2003?atlOrigin=eyJpIjoiMzJkM2ZhMzc3MTZlNDM4ZjhmY2I2NjYyMTc2NDY4NTgiLCJwIjoiaiJ9 )

Re: Support generating a NameID to put into the Subject in the AuthnRequest it issues ( https://shibboleth.atlassian.net/browse/IDP-2003?atlOrigin=eyJpIjoiMzJkM2ZhMzc3MTZlNDM4ZjhmY2I2NjYyMTc2NDY4NTgiLCJwIjoiaiJ9 )

Reviewed the code a bit, and this will have to be a 5.0 thing. The design of the NameID generation service was pretty early and has some oddness, one of which is you can’t really give it the principal name, it’s baked into the generator plugins to get it from the SubjectContext after authentication is done. Even turning that into a function slot wouldn’t really help because it would get very awkward to stipulate when it should only from there vs. from data in progress.

Best thing I think is to implement a breaking API change for 5.0 to just supply the principal name from outside the service, either exclusively, or as new methods on the relevant interfaces.

I think it’s mostly pretty simple at that point but as a use case, people will probably object to what it produces in some cases because they don’t really want a NameID, they just want a username and to abuse the NameID element to pass it since there are no other places to put it.

( https://shibboleth.atlassian.net/browse/IDP-2003#add-comment?atlOrigin=eyJpIjoiMzJkM2ZhMzc3MTZlNDM4ZjhmY2I2NjYyMTc2NDY4NTgiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/IDP-2003#add-comment?atlOrigin=eyJpIjoiMzJkM2ZhMzc3MTZlNDM4ZjhmY2I2NjYyMTc2NDY4NTgiLCJwIjoiaiJ9 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100206- sha1:40f823c )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220906/a192d758/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-07e36c74-8229-4db4-9786-35ed0a7f166b
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220906/a192d758/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-b91ed2a7-bbeb-4794-a713-73cb2d111f77
Type: image/png
Size: 457 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220906/a192d758/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-0c45c2f9-c9fc-4ed4-a718-e4c8a238359a
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220906/a192d758/attachment-0005.png>


More information about the commits mailing list