IdP 2.4 question

[Kathy E. Wright]

Thank you. My question referred to 2b which means adding new SP metadata to
our locally-maintained metadata file.

Kathy


On Mon, Jul 21, 2014 at 8:02 AM, Rod Widdowson <rdw at steadingsoftware.com>
wrote:

> Several answers depending on what you mean.
>
> 1) If you mean new metadata for an SP that you are already loading
> information about you need to ensure that you are using a reloadable
> Metadata Provider
>
>
> https://wiki.shibboleth.net/confluence/display/SHIB2/IdPMetadataProvider#IdPMetadataProvider-AboutReloadingMetadataProviders
>
> Filesystem Metadata Provider, File Backed HTTP Metadata Provider
>
> 2) If you mean that you want to add metadata for an SP that you currently
> don't know about:
>
> 2a) If you are getting your information via a federation and you think
> that the SP should be there, then wait for the next reload (see above)
>
> 2b) If this is a new SP which you are adding out of band, what most people
> do is that they manage all these SPs in their own local metadata file
> (which they then make reloadable, see above).  NOTE that you need to
> establish trust in each SP's metadata in some manner.
>
> 2c) The above two suggestions would be the recommended manner to do this.
>  But if none of these work and you need to add new metadata providers to
> the relying-party file and have that reload automatically then you need to
> make that reloadable,
> https://wiki.shibboleth.net/confluence/display/SHIB2/IdPProdConfigFiles
> is a good place to start for that.
>
> Of course none of this will happen automagically.  You will need to make
> the changes to make the IdP reload configuration and then restart it.  From
> then on it will reload automatically.
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>



-- 
Computing, Systems and Operations
ITC, 340 Computer Court
Anderson, SC 29625
kewrig at clemson.edu
(864) 656-8133
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20140721/4870a964/attachment-0001.html