shibboleth-dev - Re: SHIB Status call -- 2/4/2008) -- 12:00 pm EDT, 9 am PDT
Subject: Shibboleth Developers
List archive
- From: "Tom Scavo" <>
- To:
- Subject: Re: SHIB Status call -- 2/4/2008) -- 12:00 pm EDT, 9 am PDT
- Date: Mon, 4 Feb 2008 12:01:05 -0500
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=KB0wAIW7HqYx+fDX0qQw7wof+WVX6uhy2n/+B4h6hKKVGXzUXuTg4m+DSWg45SELWbkfIiE9DzTisMPHuj++3s8xRiAXqNsyOi6vA+/0ArOmdHt1bfuGNlvqwtCgh/hAtz6mESJGxhUZMaaGcssRsDLBlfJBmysjRFLv62sKtiE=
On Feb 4, 2008 11:22 AM,
<>
wrote:
> Agenda:
> ...
> 4) Discussion items
> -- recommendations for testing -- when to TestShib, when to
> deploy your own IdP/SP ?
I can't be on the call, so I'll give my two cents here. A deployer
should be advised to always use TestShib, even if the goal is a
bilateral deployment. In that case the sequence should be:
1. Deploy the IdP first. Test the IdP against the shib-enabled
TestShib service.
2. Shib-enable an instance of the portal (or whatever). Test this
instance against the TestShib IdP.
3. Using the SAML metadata files provided by TestShib, configure a
bilateral relationship between the IdP and the shib-enabled portal
instance. Test this bilateral deployment locally, separate from
TestShib.
This is what we will recommend to a TeraGrid Science Gateway, if and
when the issue arises.
TestShib is awesome, by the way :-)
Tom
- Re: SHIB Status call -- 2/4/2008) -- 12:00 pm EDT, 9 am PDT, Tom Scavo, 02/04/2008
Archive powered by MHonArc 2.6.16.