[JIRA] (JOIDC-82) Dyn.reg. profile config setting secretExpirationPeriod is not honored

Scott Cantor (Jira) jira at shibboleth.atlassian.net
Thu Mar 17 12:34:56 UTC 2022


Scott Cantor ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5b78efc9-1379-42cc-a3f6-56c6ea3a0007 ) *commented* on JOIDC-82 ( https://shibboleth.atlassian.net/browse/JOIDC-82?atlOrigin=eyJpIjoiMmFmZjYwNGI1Zjk5NDM0M2E5ZTA2ZjljYmU1ZDNhMDYiLCJwIjoiaiJ9 )

Re: Dyn.reg. profile config setting secretExpirationPeriod is not honored ( https://shibboleth.atlassian.net/browse/JOIDC-82?atlOrigin=eyJpIjoiMmFmZjYwNGI1Zjk5NDM0M2E5ZTA2ZjljYmU1ZDNhMDYiLCJwIjoiaiJ9 )

A GET call should never update anything, so whoever wrote that is very misguided. It would have to be a POST, and I think the semantic is unlikely to be anything but “update all this stuff”, which I did implement, so it seems like that’s good enough. I would concur with just removing the code that honors the flag and not setting it in the record. We should just stick to the overall expiration.

I would like to have a more automated means of setting up the access rules for controlling registration tokens so it would be simpler for people to get that working, but that’s likely just going to be “use a directory or Grouper for your rules” and then use attributes to handle the access control.

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

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:81e38da )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220317/13cd6ce4/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-3de55096-337e-4f6f-89e9-549a5effe4ec
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220317/13cd6ce4/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-8a45966c-3fc8-4f02-8ad8-a75b0855e4af
Type: image/png
Size: 425 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220317/13cd6ce4/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-a2737207-5b98-4669-a1a8-1a16645a66a6
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220317/13cd6ce4/attachment-0005.png>


More information about the commits mailing list