[JIRA] (JOIDC-84) OIDC SSO happens even with different ACR

Simone Avogadro (Jira) jira at shibboleth.atlassian.net
Fri Mar 18 15:22:36 UTC 2022


Simone Avogadro ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A60a84ee1-4961-471b-99d8-f67c05e24403 ) *commented* on JOIDC-84 ( https://shibboleth.atlassian.net/browse/JOIDC-84?atlOrigin=eyJpIjoiN2ZkNWYxMGE1NDJiNDMxMTlkYzgwZjAxMzc5NTczNzkiLCJwIjoiaiJ9 )

Re: OIDC SSO happens even with different ACR ( https://shibboleth.atlassian.net/browse/JOIDC-84?atlOrigin=eyJpIjoiN2ZkNWYxMGE1NDJiNDMxMTlkYzgwZjAxMzc5NTczNzkiLCJwIjoiaiJ9 )

I’m making the requiest using ther acr_values parameter as described also here [OpenID Connect | Login.gov|https://developers.login.gov/oidc/] and from what you say I understand that this values is going to be treated as an optional hint but not a requirement

So far we’ll just disable the session in order to be sure that the user will always authenticate but I guess if it would be possible to associate the tokens with the released ACR, so that subsequent calls will cause re-authentication in case they do not match

( https://shibboleth.atlassian.net/browse/JOIDC-84#add-comment?atlOrigin=eyJpIjoiN2ZkNWYxMGE1NDJiNDMxMTlkYzgwZjAxMzc5NTczNzkiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JOIDC-84#add-comment?atlOrigin=eyJpIjoiN2ZkNWYxMGE1NDJiNDMxMTlkYzgwZjAxMzc5NTczNzkiLCJwIjoiaiJ9 )

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#100197- sha1:003460b )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220318/6b18319a/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-599cf517-5760-458b-998a-e849c6485796
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220318/6b18319a/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-932eed72-6b4d-4018-82dd-95ad4a420898
Type: image/png
Size: 425 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220318/6b18319a/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-238b51a0-03c7-4d1a-94f3-196c0b461b3d
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220318/6b18319a/attachment-0005.png>


More information about the commits mailing list