Skip to Content.
Sympa Menu

mace-opensaml-users - Re: Charset restrictions in NameIdentifier

Subject: OpenSAML user discussion

List archive

Re: Charset restrictions in NameIdentifier


Chronological Thread 
  • From: Tom Scavo <>
  • To: "" <>
  • Cc:
  • Subject: Re: Charset restrictions in NameIdentifier
  • Date: Tue, 9 Aug 2005 10:45:56 -0400
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Sb+Xh+k83VcU7Imttd2ADVWK4Ytw6k3s/YvmF1Umu+/GUh5l4KumXS6CriU50lPfH/6MT09VW+HPvkhn6+4kTEIcVArF5XwKA2Pgiys7tnWT2LXRPFfxpLwPK7FOJptTrmPLhODu4JY9TWDE9nnW3GZUrmA7grUl7F7QUIrbj+g=
On 8/9/05,


<>
wrote:
>
> Are there restrictions on the character set used in the NameIdentifier or
> the AttributeValue contents?
> Is there some mandated or recommended encoding?

In some cases, yes. For example, a NameIdentifier with format
X509SubjectName has certain encoding restrictions inherited from
[XMLSig] (see section 7.3 of the SAML 1.1 core spec). Our project
relies on X509SubjectName, so I have it on my TODO list to implement
this encoding, but I haven't got around to it yet.

I don't believe there is any inherent restriction on AttributeValue.

Hope this helps,
Tom

Archive powered by MHonArc 2.6.16.

Top of Page