RE: [security-services] Endianness of Artifact Typecode?

[Hal Lockhart <hal.lockhart@entegrity.com>]

Title: [security-services] Endianness of Artifact Typecode?

Prateek,

 

Thanks.

 

Perhaps in the next revision you could add this clarification and perhaps an example of a correctly encoded artifact value.

 

Hal

-----Original Message-----
From: Mishra, Prateek [mailto:pmishra@netegrity.com]
Sent: Tuesday, March 19, 2002 10:45 AM
To: 'Hal Lockhart'; 'security-services@lists.oasis-open.org'
Cc: Mishra, Prateek
Subject: RE: [security-services] Endianness of Artifact Typecode?

Hal,

 

Notice that the artifact is embedded in the search or path component of the URL. The entire

artifact is therefore transmitted as a text object. After removing the B64 encoding, the type code should appear as originally constructed - first byte holds the higher-order bits,  the second byte the lower-order bits. The key here is that no "binary" format is being used.

 

 

- prateek

-----Original Message-----
From: Hal Lockhart [mailto:hal.lockhart@entegrity.com]
Sent: Monday, March 18, 2002 9:15 AM
To: 'security-services@lists.oasis-open.org'
Cc: 'Mishra, Prateek'
Subject: [security-services] Endianness of Artifact Typecode?

Is there an official answer to this?

Hal

 -----Original Message-----
From:   Ryan Eberhard 
Sent:   Monday, March 18, 2002 8:05 AM
To:     Hal Lockhart
Subject:        Question on section 4.1.1.8 of SAML Bindings and Profiles

Hal,

In the Artifact Format section (4.1.1.8), it defines an artifact as beginning with a two-byte type code, but it doesn't specify the endianness of this value, e.g. it says "TypeCode := Byte1Byte2".  Can you verify the expected byte order?

Thanks,
Ryan