[JIRA] (IDP-2133) seckeygen.sh not updated on upgrade to v5
Rod Widdowson (Jira)
jira at shibboleth.atlassian.net
Fri Jun 23 08:11:01 UTC 2023
Rod Widdowson ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=59fb32bbc24efb3c4ed3c977 ) *commented* on IDP-2133 ( https://shibboleth.atlassian.net/browse/IDP-2133?atlOrigin=eyJpIjoiNzZiODAwYjVlZmU5NDY0MTg5NjVkYWU5OGU5YTZjMWEiLCJwIjoiaiJ9 )
Re: seckeygen.sh not updated on upgrade to v5 ( https://shibboleth.atlassian.net/browse/IDP-2133?atlOrigin=eyJpIjoiNzZiODAwYjVlZmU5NDY0MTg5NjVkYWU5OGU5YTZjMWEiLCJwIjoiaiJ9 )
>
>
>
> I was thinking it worked the way the plugins do, with the “old” state
> established with the old classpath.
>
>
sigh, you are right of course.
The flip side is that this means that we’ll totally miss the new modules (because they don’t exist in the old install). But that’s fine; we can either make them required (so, enabled alongside IdP.core) or (more likely) have them enabled automatically either because they are needed and not in the current bundle (logically equivalent to a new install) or because we always do. Let’s face it, you cannot run an IdP without IdP.commandline or IdP.edit-webapp and it’s disastrous to disable them (not sure if you can) so having a way of forcing them back into existence seems sensible. Need to see what it looks like in the code.
( https://shibboleth.atlassian.net/browse/IDP-2133#add-comment?atlOrigin=eyJpIjoiNzZiODAwYjVlZmU5NDY0MTg5NjVkYWU5OGU5YTZjMWEiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/IDP-2133#add-comment?atlOrigin=eyJpIjoiNzZiODAwYjVlZmU5NDY0MTg5NjVkYWU5OGU5YTZjMWEiLCJwIjoiaiJ9 )
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#100227- sha1:d138f7b )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20230623/0666e2c7/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-743ce914-566c-4ac1-963a-67c0573311ca
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230623/0666e2c7/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-12dab930-d2bb-40b7-9f6d-053225732864
Type: image/png
Size: 345 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230623/0666e2c7/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-35c8e1e1-a2f1-41f1-81a4-a7754fcb0450
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230623/0666e2c7/attachment-0005.png>
More information about the commits
mailing list