[JIRA] (JOIDC-117) Take clock skew into account in revocation lifetimes

[Henri Mikkonen (Jira)]

Henri Mikkonen ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A1614c4a5-c89e-4edc-9421-990bd6ea85fd ) *created* an issue

IdP Plugin - OIDC OP ( https://shibboleth.atlassian.net/browse/JOIDC?atlOrigin=eyJpIjoiODcwODcxYjY4MTQyNDI3N2IxZmRlNWM2OGEyZjY4YjYiLCJwIjoiaiJ9 ) / Bug ( https://shibboleth.atlassian.net/browse/JOIDC-117?atlOrigin=eyJpIjoiODcwODcxYjY4MTQyNDI3N2IxZmRlNWM2OGEyZjY4YjYiLCJwIjoiaiJ9 ) JOIDC-117 ( https://shibboleth.atlassian.net/browse/JOIDC-117?atlOrigin=eyJpIjoiODcwODcxYjY4MTQyNDI3N2IxZmRlNWM2OGEyZjY4YjYiLCJwIjoiaiJ9 ) Take clock skew into account in revocation lifetimes ( https://shibboleth.atlassian.net/browse/JOIDC-117?atlOrigin=eyJpIjoiODcwODcxYjY4MTQyNDI3N2IxZmRlNWM2OGEyZjY4YjYiLCJwIjoiaiJ9 )

Issue Type: Bug Affects Versions: 3.2.0 Assignee: Henri Mikkonen ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A1614c4a5-c89e-4edc-9421-990bd6ea85fd ) Components: Revocation Endpoint, Token Endpoint Created: 06/Jul/22 7:52 AM Priority: Trivial Reporter: Henri Mikkonen ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A1614c4a5-c89e-4edc-9421-990bd6ea85fd )

The lifetimes for revocation records are currently taken either from the revocation profile configuration (when revoking the chain), or via expiration time of the token (when revoking a single token, possible since 3.2.0). The revocation lifetime calculation should also take configurable clock skew into account, as the clock skew value is already considered during the token claims set validation in userinfo, introspection and revocation endpoints.

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

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#100201- sha1:0577670 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220706/c1aae3ce/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-0b79cb3d-4d1c-438a-9ffe-449b379254a8
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220706/c1aae3ce/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-trivial-e332e0bc-6bae-45cb-94a1-d413e275c842
Type: image/png
Size: 563 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220706/c1aae3ce/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-fbab05d6-8ad3-47cf-890a-6ad6852deeb7
Type: image/png
Size: 425 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220706/c1aae3ce/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-4b35bcd1-0540-4fe5-a1ff-6cc5460a109e
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220706/c1aae3ce/attachment-0007.png>