Shibboleth Developers

[Peter Williams <>]

The interworking partner uses shib2 idp.

Another interworking partner uses shib2.1 sp.

Being open standards, I happen to use a non shib idp and non shib sp. (I'm 
keeping my shib sp src build knowhow in my back pocket, for now. It will be 
useful later to cheaply build out the spokes in our hub/spoke nerwork. 
Shib2.x sp is clearly maturing very fast, for commercial exploitation.)

First, (today) Im addressing shib idp to ping sp (using saml2). This is 
because the patner is relatively expert in shib config and coding.

Then, ill do our ping idp (with slo) to their shib sp (with soap based slo).

Both those links expect to work at commercial grade levels of service.

Id target all this at shib users normally, but someone will just claim im 
abusing the neophytes focussing on basic  cgi attributes and elementary sso, 
etc. As its more complex than that , I came here. Perhaps I was wrong to do 
so (yet again). Perhaps there is no forum for this. In which case, I may just 
give up till someone else solves it, in a manner the bottom of the class can 
understand (ie me).

-----Original Message-----
From: Peter Schober 
<>
Sent: Saturday, May 09, 2009 11:30 AM
To: 

 
<>
Subject: Re: [Shib-Dev] sessionid, previous session, assertions - web   
gardens, web farms, concurrent sessionstate locking....


* Peter Williams 
<>
 [2009-05-09 19:58]:
> Assume the SP is NOT based on the Shib SP code base.
> [...] Assume we have a tested/complying SAML2 IDP with both
> foreground and SOAP-based SLO.

Assuming you neither use the Shib SP nor the Shib IdP this is probably
the wrong mailing list?
cheers,
-peter