Hi Fred,
I remember somewhere in the spec it recommends the use of Base64 encoding for
sourceID. I vote for use the Base64 encoding.
Emily
SunONE products
Sun Microsystems, Inc.
408-276-5480
> Content-return: allowed
> Date: Thu, 18 Apr 2002 16:30:48 -0400
> From: "Chen, Fred" <>
> Subject: [saml-dev] SAML artifact source id config.
> To:
> List-Owner: <mailto:>
> List-Post: <mailto:>
> List-Subscribe: <http://lists.oasis-open.org/ob/adm.pl>,
<mailto:?body=subscribe>
> List-Unsubscribe: <http://lists.oasis-open.org/ob/adm.pl>,
<mailto:?body=unsubscribe>
> List-Archive: <http://lists.oasis-open.org/archives/saml-dev/>
> List-Help: <http://lists.oasis-open.org/elists/admin.shtml>,
<mailto:?body=help>
> List-Id: <saml-dev.lists.oasis-open.org>
>
> Hi folks,
>
> I am writing some code to support saml browser/artifact profiling.
> According to draft-sstc-bindings-model-15, In section 4.1.1.6, it says "In
> steps 4 and 5, the destination site, in effect, dereferences the one or more
> SAML artifacts in its possession in order to acquire the SAML authentication
> assertion ...."
> I run into a problem that when the destination site composes a config file
> in its possession. As its partner sends the 20-byte code, which is typically
> a SHA-1 output with some non-displayable characters, you must have awared
> that a conversion from byte array into plain text is needed. This may cause
> some man made error or code burden/incompatibility on the destination site.
>
> How about its partner sends the hex string or Base64 encoded string of the
> SourceID for the agreement/configuration purpose.
>
> Please note, this doesn't affect the artifact format of section 4.1.1.8.
>
> Any thought?
>
> -Fred
>
>
>
>
>
>
>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
