Skip to Content.
Sympa Menu

shibboleth-dev - Re: SAML implementations besides Shib

Subject: Shibboleth Developers

List archive

Re: SAML implementations besides Shib


Chronological Thread 
  • From: Tom Scavo <>
  • To: Sean Mehan <>
  • Cc: Alistair Young <>, Scott Cantor <>, Shibboleth Development <>
  • Subject: Re: SAML implementations besides Shib
  • Date: Wed, 27 Apr 2005 11:49:49 -0400
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Yg7eI/EzS1qeUWWZtTqIRy5zH60gTFESMhzFQjnmbm691ODlzuQO0SXaHj5HsBcFHhSwYVOAc8v0QgpvdRdMbtDf+1l+mOczdVVWC6HY9UzlB05j45/FYjfxTjeD/vwowcSDH9Z6qUJOgLt6LV7mmdacJN1U2O8WCK30ex45bvk=
On 4/27/05, Sean Mehan
<>
wrote:
>
> This now leads to a new SAML profile, in the first instance just
> extending
> shibboleth's Browser/POST:
>
> 1) User accesses resource at SP
> 2) SP sends GET request to user's IdP after WAYF finds out where that
> is.
> 3) IdP authenticates user and sends AuthenticationStatement back to SP.
> 4) SP sends AttributeRequest to SP
> 5) NEW - IdP queries SP's ADDI service for required attributes and any
> vendor specific mappings based on the resource the user wants to access.
> 6) IdP maps required attributes to local set and releases them based on
> ARP
> 7) SP makes decision based on incoming attributes from the IdP.

Does the attribute query block while the ADDI exchange takes place?

Tom

Archive powered by MHonArc 2.6.16.

Top of Page