sharing Shibboleth SP configuration data

[Dave Perry]

I shared ours with someone who wanted to get a certain webapp (moodle) working, and had read on a forum that I had it sussed. I just gave him the bits he needed, mainly from attribute-map and shibboleth2 but also (in our case) Apache.


Dave

_________________________________________________
Dave Perry
eLearning Technologist, Hull College Group

Room L34 - Queens Gardens Library
Wilberforce Drive, Queen's Gardens, Hull, HU1 3DG
Extension 2230 / Direct Dial 01482 381930

* Need a fast reply? Try elearning at hull-college.ac.uk *

-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: 20 October 2014 20:33
To: Shib Users
Subject: Re: sharing Shibboleth SP configuration data

On 10/20/14, 1:27 PM, "Ken Weiss" <ken.weiss at ucop.edu> wrote:

>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?

I really don't know what people would consider sensitive. I suppose if there's anything, knowing what headers you're using might provide somebody with at least a head start on trying to build an exploit, but since everybody uses the defaults mostly, that doesn't mean much.

>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.

Unless you're going to change defaults, nothing in the metadata is going to be even very difficult for somebody to guess.

-- Scott

--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net

**********************************************************************
This message is sent in confidence for the addressee
only. It may  contain confidential or sensitive
information.  The contents are not to be disclosed
to anyone other than the addressee.  Unauthorised
recipients are requested to preserve this
confidentiality and to advise us of any errors in
transmission.  Any views expressed in this message
are solely the views of the individual and do not
represent the views of the College.  Nothing in this
message should be construed as creating a contract.

Hull College owns the email infrastructure, including the contents.

Hull College is committed to sustainability, please reflect before printing this email.
**********************************************************************

TEXT