Automating the generation of IdP metadata

Franck Mangin FranckMangin at fico.com
Fri Feb 12 05:52:13 EST 2016


Hi All,

I am new to Shibboleth, and I wanted for first congrat the team on the outstanding Wiki documentation: this got me running in a couple days with no SAML experience whatsoever :)

I am trying to automate the IdP installation & configuration, and I am running into issues with the IdP metadata.
Install.bat generates a sample idp-metadata.xml which I would like to leverage, in particular because it contains the right security keys generated from install properties (I am supplying both idp.sealer.password and idp.keystore.password for the install).

However the auto-generated file also contains incorrect Locations for the ArtifactResolutionService and AttributeService elements, because my https port is not 8443. I looked up the GenerateMetadata.java source code and it looks like :8443 is hardcoded to be appended to URLs, apparently for locations that are deemed to require secure connections.
Is there any install setting I could use to override this (I suspect not given the source code)?

It looks like the only alternatives I have would be to either:

-          Write my own generator (sucks, I'm pretty much guaranteed to get it wrong)

-          Parse the auto-generated idp-metadata.xml and replace the bad URLs (pretty much what I'm doing right now)
The metadata returned by https://.../idp/Shibboleth seems to come right from the idp-metadata.xml file, so no hope there I assume?

Am I missing any better alternative?

Thanks for your help,
Franck

This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160212/40d86f85/attachment.html>


More information about the users mailing list