RE: [saml-dev] AssertionArtifact: Construction question (byte ord er,spaces)

["Philpott, Robert" <rphilpott@rsasecurity.com>]

  0, 1, 100, 101, 102, ..., 119, 200, 201, 202, ..., 219 (42 bytes)

is the correct byte-order representation of the data, which is then encoded
as a Base64 string.

Rob Philpott 
RSA Security Inc. 
The Most Trusted Name in e-Security 
Tel: 781-515-7115 
Mobile: 617-510-0893 
Fax: 781-515-7020 
mailto:rphilpott@rsasecurity.com 


-----Original Message-----
From: Kremp, Juergen [mailto:juergen.kremp@sap.com] 
Sent: Thursday, November 21, 2002 11:37 AM
To: 'saml-dev@lists.oasis-open.org'
Subject: [saml-dev] AssertionArtifact: Construction question (byte order,
spaces)

Dear Experts,

the SAML Bindings speficication describes the Assertion Artifact creation
like this:

SAML_artifact := B64(TypeCode RemainingArtifact)
TypeCode      := Byte1Byte2

with detailled data:

TypeCode          := 0x0001
RemainingArtifact := SourceID AssertionHandle
SourceID          := 20-bytes
AssertionHandle   := 20-bytes


My question has two parts:

(1) What is the considered byte order of the "TypeCode" for the first form
of the artifact (0x0001)?
(2) Has the <space> character in the definitions of "SAML_artifact" and
"RemainingArtifact" a literal meaning or separates it just the words.


Example: 

Let the SourceID by the 20-byte sequence (100, 101, 102, ..., 119) 
and the AssertionHandle by the 20-byte sequence (200, 201, 202, ..., 219).

Will the correct artifact then be the Base64-representation of

  0, 1, 100, 101, 102, ..., 119, 200, 201, 202, ..., 219 (42 bytes)

or of 

  1, 0, 100, 101, 102, ..., 119, 200, 201, 202, ..., 219 (42 bytes)

or of 

  0, 1, 32, 100, 101, 102, ..., 119, 32, 200, 201, 202, ..., 219 (44 bytes)

or of 

  1, 0, 32, 100, 101, 102, ..., 119, 32, 200, 201, 202, ..., 219 (44 bytes)


The specification is not that clear about that point, especially an example
is missing.

Juergen Kremp
SAP AG

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>