metadata generation
Jeff Masiello
jmasiello at actionet.com
Fri Jun 20 14:38:44 EDT 2014
I'm sure it will. Thanks:)
Jeff,
Try starting here:
https://wiki.shibboleth.net/confluence/display/SHIB2/Metadata#Metadata-MethodsforSupplyingMetadata
"Common federation" ~ = "a common metadata aggregate and underpinning policy that both this IdP and this SP trust, read from, and publish to"
If you have one IdP and many SP's that are not super technical, it's usually easiest to maintain a metadata file for the IdP at the IdP, a metadata file for all SP's somewhere(or at the IdP) loaded by the IdP, and set up a configuration generator for SP's. TestShib's SP configuration generator is basically sed on a template shibboleth2.xml.
Hope this helps,
Nate.
On Jun 20, 2014, at 12:32 PM, Jeff Masiello <jmasiello at actionet.com<mailto:jmasiello at actionet.com>>
wrote:
The term Common Federation sort of loses me. In our system, specifically, we have one IdP and multiple SP's from various places and add new SP's randomly. I guess what I'm trying to find is a good common practice to exchange that information that isn't tedious. Our users who install the SP which we supply generally are not super technical.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20140620/e8ef9ca5/attachment.html
More information about the users
mailing list