[JIRA] (JMETAGEN-5) Consider generalizing into a replacement for SP's metagen script

[Scott Cantor (Jira)]

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

Re: Consider generalizing into a replacement for SP's metagen script ( https://shibboleth.atlassian.net/browse/JMETAGEN-5?atlOrigin=eyJpIjoiM2M3ZTA1YTI0MWVkNDM4M2E0Y2M2NjVjNzRmNTNjZjAiLCJwIjoiaiJ9 )

I have a fairly functional strawman on a dev branch that illustrates the general idea. I have basic structure, roles, keys, and endpoints more or less working.

My idea is to define an interface in OpenSAML that provides the methods to obtain all the details needed to put into the metadata and transplant the Velocity-based code and templates into there to mechanically generate the XML. The templates will by default just be in the opensaml jar. In principle the plugin could contain an optional module that when enabled actually copies out the templates into the file system for customization.

The current CLI argument class I modified from the existing plugin will then be changed to implement that interface, supplying the necessary information directly from the CLI arguments, but without making the generator actually depend on the CLI itself.

Then it just needs extending to add in all the various bits and whistles potentially needed to generate.

I hadn’t really considered it but it does occur to me that it would be potentially possible to define a Spring bean that implements this new OpenSAML interface inside the IdP, and could I suppose populate itself from the IdP’s internals rather than from a CLI argument set. The IdP’s metadata could then be generated on the fly, something I of course never wanted to support, but it’s probably not a ton of work to cook up something skeletal, and properties could be defined to add things like MDUI and the like, allowing the outside config to drive the generation.

Either way, the installer should be much simpler, it either just supplies a custom impl of this interface and runs the generator, or it does nothing and we move to a dynamic approach that will run any time.

( https://shibboleth.atlassian.net/browse/JMETAGEN-5#add-comment?atlOrigin=eyJpIjoiM2M3ZTA1YTI0MWVkNDM4M2E0Y2M2NjVjNzRmNTNjZjAiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JMETAGEN-5#add-comment?atlOrigin=eyJpIjoiM2M3ZTA1YTI0MWVkNDM4M2E0Y2M2NjVjNzRmNTNjZjAiLCJwIjoiaiJ9 )

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#100230- sha1:e339e49 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20230706/4016ada9/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-fb669e9c-948f-4b80-91ab-99b39e97d271
Type: image/png
Size: 302 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230706/4016ada9/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-2c3af4bd-dd46-48a8-9cf7-512c6dd6681b
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230706/4016ada9/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-c64d3597-d85e-4c55-b3e0-982c2ed4421f
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230706/4016ada9/attachment-0005.png>