sharing Shibboleth SP configuration data

[Ken Weiss]

I am tasked with documenting our Shibboleth SP configuration so that other institutions can replicate our work. What, if any, elements in the shibboleth2.xml or attribute-map.xml files should I consider sensitive enough to redact before publishing them? Nothing stuck out at me as particularly sensitive, other than maybe the ACL list for the 'Status' handler' in shibboleth2.xml. Did I miss anything?

I assume there is nothing in the SP metadata to worry about. That information gets published by InCommon as part of the production metadata aggregate, so it's available to anyone with an Internet connection anyway.

--Ken

------------------------------------------------------------
Ken Weiss                                 ken.weiss at ucop.edu<mailto:ken.weiss at ucop.edu>
UC Office of the President              510-587-6311 (office)
California Digital Library              916-905-6933 (mobile)
UC Curation Center
415 20th Street, 4th Floor
Oakland, CA 94612

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20141020/6a5f7e7b/attachment.html