[JIRA] (JOIDC-152) Implement maximum refresh time and/or maximum refresh uses.

[Henri Mikkonen (Jira)]

Henri Mikkonen ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A1614c4a5-c89e-4edc-9421-990bd6ea85fd ) *commented* on JOIDC-152 ( https://shibboleth.atlassian.net/browse/JOIDC-152?atlOrigin=eyJpIjoiNzg1NzZhZWJjY2RjNDUyZGE0YTljYzg0ZGExZWY0NTciLCJwIjoiaiJ9 )

Re: Implement maximum refresh time and/or maximum refresh uses. ( https://shibboleth.atlassian.net/browse/JOIDC-152?atlOrigin=eyJpIjoiNzg1NzZhZWJjY2RjNDUyZGE0YTljYzg0ZGExZWY0NTciLCJwIjoiaiJ9 )

After some internal discussions it feels best that we change the currently existing profile configuration option refreshTokenLifetime to refer to the maximum lifetime of the chain of refresh tokens. That terminology would then be better in-line with the other parts of the IdP stack.

A single refresh token lifetime would then need another profile configuration option. It should refer to a timeout of a refresh token.

I know, it’s not ideal to change the meaning of an existing profile configuration option, but this move still feels right. How does this sound for you, Pierre Sagne ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3Ab389f93c-082f-42b2-8684-ac3e951ab163 ) Simone Avogadro ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A60a84ee1-4961-471b-99d8-f67c05e24403 ) ?

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

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#100223- sha1:02266b8 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20230427/510c54e4/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-fffa4894-103d-487c-96b0-54624937ad90
Type: image/png
Size: 302 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230427/510c54e4/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-c5263563-3aae-45dd-8c3b-a3cfe785ee41
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230427/510c54e4/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-2fd00a75-bee9-4953-b89b-a3412e0368e8
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230427/510c54e4/attachment-0005.png>