OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

saml-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [saml-dev] Artifact Format

Thanks Tom.

Yes, I could not find anything in the conformance doc also.
So, I could define
Artifact = [Typecode MyFooBar(nn)]
Where TypeCode := 0x0100 (e..g)


On 3/13/06, Tom Scavo <trscavo@gmail.com> wrote:
On 3/13/06, prasanta behera <pkb.prasanta@gmail.com> wrote:
> SAML 2.0 Binding document  ("Artifact Format" - line 1046) defines artifact
> to be:
>  Artifact = [TypeCode(2) EndPointIndex(2) SourceID(20) MessageHandle(20)]
>  Length is denoted in brackets.
>  Does  SAML 2.0 compliant server MUST follow the above format?

It must *support* the above format, yes (although I can't find
explicit wording to this effect in the conformance doc).

>  How can I extend it?
>  Artifact = [TypeCode(2) EndPointIndex(2) SourceID(20) MessageHandle(20)
> FOOBAR(nn)]

Sure, you are free to define your own artifacts types and, hence, your
own bindings, why not? (Type codes 0x0001 thru 0x0004 are taken,

>  Is this allowed? Any issue/restriction/issues? etc.

Other than the fact you won't interoperate with anybody else, no. :-)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]