Shib 1.3
Cantor, Scott
cantor.2 at osu.edu
Wed Oct 31 11:07:47 EDT 2012
On 10/31/12 10:59 AM, "Lohr, Donald" <lohrda at jmu.edu> wrote:
>We have Shib v2 on our roadmap, but are not their yet. All of the SP's
>we interact with are InCommon Participants. We have been asked to
>connect Shib to a new non-InCommon Service Provider.
Shibboleth doesn't know anything about InCommon, so there's no difference
to it. InCommon is a way of managing metadata and trust, it doesn't
preclude others.
>Being new to Shib, especially 1.3 (which is using SAML 2x),
Shibboleth 1.3 does not support SAML 2. If your new SP is SAML 2 only,
then you cannot connect to it.
> can I configure my current Shib
>1.3 environment to jointly get/send metadata to 1) InCommon and 2) this
>new non-Incommon SP?
Yes, it has roughly similar capabilities in terms of supporting multiple
metadata files.
>If so, what documentation exists that can guide me through making the
>necessary configuration changes to my existing Shib 1.3 environment?
The old 1.3 documentation in the wiki, I suppose.
-- Scott
More information about the users
mailing list