mace-opensaml-users - Re: SAML 1.1 browser/artifact profile
Subject: OpenSAML user discussion
List archive
- From: Tom Scavo <>
- To: Mintoo C <>
- Cc:
- Subject: Re: SAML 1.1 browser/artifact profile
- Date: Fri, 4 Mar 2005 12:30:36 -0500
- 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:references; b=ZCYSxmzjiRvkWYTHrvdz5Tp/06DldKXWU3xxkZDASg0GTHXw9PPO5D6is01nSppT/xVcyYYVAxvJwidWuXYdiGtiSSEF9g8351tQHIClFG8TgmBPmapti2BtwEPNo2V8+LJzsquxKdVdE9gzt0vohTtgzUmIxmB16dDWq/IEk5Q=
On Fri, 4 Mar 2005 11:03:32 -0500, Mintoo C
<>
wrote:
>
> We will primarily be using the Browser/Artifact Profile (not sure if
> support for destination-Sit-first or Source-Site-First or both is
> required currently).
SAML 1.1 specifies identity-provider-first profiles (what you call
"source-site-first") so that is what's supported in OpenSAML at the
moment.
> 3/ The test suite doesn't seem to have a test class for the
> Browser/Artifact profile. Maybe i'm missing something here.
Basic code support for SAML artifacts (type 0x0001 and 0x0002) was
committed to OpenSAML just last month. Support for the
Browser/Artifact profile will follow. Consequently, the next version
of OpenSAML will support SAML 1.1 Browser/Artifact profile (in
addition to Browser/POST).
By the way, you will find JUnit tests for SAML artifacts in CVS. A
test for the profile is forthcoming.
Tom
- SAML 1.1 browser/artifact profile, Mintoo C, 03/04/2005
- Re: SAML 1.1 browser/artifact profile, Tom Scavo, 03/04/2005
- RE: SAML 1.1 browser/artifact profile, Scott Cantor, 03/04/2005
Archive powered by MHonArc 2.6.16.