[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 12:24:20 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=eyJpIjoiN2I4Mjk0YzA1YmE0NDk2N2E1NjRkYmYwNTYxODEzM2QiLCJwIjoiaiJ9 )

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

SAML simply doesn’t support what you’re after here, it’s not a matter of want. Embedding a NameID in the request is not a hint to populate the form, but rather a demand that the result be equivalent. Other protocols do obviously have this feature, SAML just didn’t. The whole “separate factors” approach to authentication wasn’t common at the time, the most common MFA methods back then used PINs and didn’t combine independent systems.

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

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/49b31b1f/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-1743bb76-81b9-4b02-9e09-7bf617dfc02e
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220906/49b31b1f/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-97066bd2-fd74-4419-8eb0-90544ecd2b4e
Type: image/png
Size: 457 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220906/49b31b1f/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-e3ed3ab9-c407-440e-97db-0544bb298538
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220906/49b31b1f/attachment-0005.png>


More information about the commits mailing list