Shibboleth Developers

[Tom Scavo <>]

On Sat, Sep 25, 2010 at 1:10 PM, Scott Cantor 
<>
 wrote:
>
> It is necessary to articulate an expectation of possible behvaior. Since an
> IdP MAY send anything it wants at any time, including an error, at the end
> of the day, that's what SPs have to handle.

That's a start. Here are a couple of other items that may need to be 
discussed:

- the effect of isPassive="true" in consent-based SSO
- the fact that persistent name IDs need to be redundantly asserted as
attributes

Speaking of persistent identifiers, how does the SP ask for a
"persistent, non-reassigned identifier"? There are a number of
attributes that satisfy that requirement, so how does the SP encode
its requirement for one of them?

Tom