[JIRA] (JOIDC-100) Releasing IAT, EXP and NBF claims from the UserInfo endpoint
Simone Avogadro (Jira)
jira at shibboleth.atlassian.net
Fri Apr 22 15:46:06 UTC 2022
Simone Avogadro ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A60a84ee1-4961-471b-99d8-f67c05e24403 ) *commented* on JOIDC-100 ( https://shibboleth.atlassian.net/browse/JOIDC-100?atlOrigin=eyJpIjoiODM5MmM0ZmQxMWNjNGVkNDhkMGY3MWM1ZjZiMTJhOGIiLCJwIjoiaiJ9 )
Re: Releasing IAT, EXP and NBF claims from the UserInfo endpoint ( https://shibboleth.atlassian.net/browse/JOIDC-100?atlOrigin=eyJpIjoiODM5MmM0ZmQxMWNjNGVkNDhkMGY3MWM1ZjZiMTJhOGIiLCJwIjoiaiJ9 )
More generally I’ve tried reading the spec but I don’t see specific restrictions on the UserInfo endpoint regarding thse three claims.
I understand that these are used and reserved in other contexts and it’s generally wise to lock down reserved keywords usage more widely but given the fact that the IDé is usually managed by people who should “know what they are doing” a flag to allow them pass-thru so that deployers might decide their own generation strategy.
If you instead prefer to provide IDP-centric generation I propose the following semanthincs:
* iat: instant
* exp: =iat+duration (a configurable parameter)
* nbf: =iat-grace_duration (a configurable parameter)
( https://shibboleth.atlassian.net/browse/JOIDC-100#add-comment?atlOrigin=eyJpIjoiODM5MmM0ZmQxMWNjNGVkNDhkMGY3MWM1ZjZiMTJhOGIiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JOIDC-100#add-comment?atlOrigin=eyJpIjoiODM5MmM0ZmQxMWNjNGVkNDhkMGY3MWM1ZjZiMTJhOGIiLCJwIjoiaiJ9 )
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#100198- sha1:943baf4 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220422/59d3bcab/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-fe23e2fb-a967-4abf-9305-de45f54d7501
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220422/59d3bcab/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-9954150f-4a1a-4684-bc6a-5d66334af5e4
Type: image/png
Size: 457 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220422/59d3bcab/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-92b9a1ab-ab9f-47f5-a534-ed4dba96d683
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220422/59d3bcab/attachment-0005.png>
More information about the commits
mailing list