mace-opensaml-users - Re: [OpenSAML] Regarding SAML artifact size
Subject: OpenSAML user discussion
List archive
- From: Siva prakash I V <>
- To:
- Subject: Re: [OpenSAML] Regarding SAML artifact size
- Date: Thu, 18 Nov 2010 18:18:55 +0530
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=qLjiJfS6eXZIz3zxQ00pCZqgybHs2QtdzqmslKmT4uHQVepXtH4R+usrD8/bX6ngBt PVi8vmdMvNSdFKOEpYlZUSGmyXxNeCaD3c6rLwyo6S5qRX9sSWwWE2QfLC8BDJ6Mt1cp vYe9tOCmSv5hsstl1OjIu4l0tjdJUVBAixMjo=
Thanks alot for the information.
The other types also do not help my requirement.
On Thu, Nov 18, 2010 at 6:02 PM, Chad La Joie <> wrote:
You can define your own, but it won't be interoperable with anyone else.
Have you looked at the other types? I mispoke before, it's the type 2 artifacts that have the easier to use format because it doesn't hash the URL, so you can just do a string compare. That might be more to your liking since the URL can be arbitrarily long.
On 11/18/10 7:20 AM, Siva prakash I V wrote:As I'm new to SAML, please clarify me one thing.
If I'm not wrong, type code 0x0004 uniquely identifies the mentioned 44
byte character sequence which is already implemented in Open SAML.
But as I'm forced to generate a MESSAGE_HANDLE of more than 20 bytes
which does't allow me to use the format of type code 0x0004, can I use
a different type code which uniquely defines my custom format ? Is this
recommended as long as the source and destination sites can go with.
On Thu, Nov 18, 2010 at 5:25 PM, Chad La Joie <<mailto:>> wrote:http://itumi.biz <http://itumi.biz/>
OpenSAML already has support for the various defined artifacts, so
you don't need to implement those specifically. As far as which
type to use, it's up to you. Personally I find type 4 artifacts,
the one you're talking about, a lot easier to use than the other
ones because it doesn't require looking up data via hashes or other
such work.
On 11/18/10 6:45 AM, Siva prakash I V wrote:
Hi,
I'm trying to implement SAML artifact binding. I've read that a SAML
artifact needs to be a 44 byte sequence
containing TYPECODE (2 bytes) ENDPOINTINDEX (2 bytes) SOURCEID (20
bytes) MESSAGE_HANDLE(20 bytes).
Is this Format along with the accommodated size is a MANDATORY
one or a
RECOMMENDED one.
As an issuer of Artifact can I create an artifact having more
than 20
byte MESSAGE_HANDLE. Is this an acceptable one?
Thanks,
Siva Prakash
--
Chad La Joie
trusted identities, delivered
- [OpenSAML] Regarding SAML artifact size, Siva prakash I V, 11/18/2010
- Re: [OpenSAML] Regarding SAML artifact size, Chad La Joie, 11/18/2010
- Re: [OpenSAML] Regarding SAML artifact size, Siva prakash I V, 11/18/2010
- Re: [OpenSAML] Regarding SAML artifact size, Chad La Joie, 11/18/2010
- Re: [OpenSAML] Regarding SAML artifact size, Siva prakash I V, 11/18/2010
- Re: [OpenSAML] Regarding SAML artifact size, Chad La Joie, 11/18/2010
- Re: [OpenSAML] Regarding SAML artifact size, Siva prakash I V, 11/18/2010
- Re: [OpenSAML] Regarding SAML artifact size, Chad La Joie, 11/18/2010
Archive powered by MHonArc 2.6.16.