Re: saml-dev RE: [saml-dev] Question about the base64 encoding inBrowser/POST profile

> The questions I have are about base64 and whether any of that is
 > affected by character encoding.

No, it's just arbitrary bytes to base64; it doesn't know if it's UTF8, 
UTF16, Shift-JIS, gb-xxxx, etc.

I believe the problem is that the SAML schema doesn't allow you to say 
*which* encoding is used.  I can see three options:
   You could add a "saml:encoding" attribute to any element whose 
content is base64.  Most flexible, most likely to cause interop problems.
   Require all such base64 fields to be UTF-8.  Possibly problematic if 
the containing document is in a different encoding
   Require all such base64 fields to be in the same encoding as the 
containing document.

	/r$