RE: [saml-dev] Constrain existing ID attributes?

[Irving Reid <Irving.Reid@baltimore.com>]

> From: Eve L. Maler [mailto:eve.maler@sun.com]

[ talk about changing the existing SAML assertionID, requestID etc. to
xsd:ID type ]

> Can implementers please weigh in and let us know (a) if doing 
> this would 
> break their current implementations and (b) if so, would it 
> be a problem 
> to update their implementations to account for this in their 
> SAML V1.1 work?

Baltimore's current implementation does not guarantee that SAML IDs meet the
correct syntax for xsd:ID; we're using base64 of arbitrary binary data, so
the ID may begin with (and contain) invalid characters.

It would not be a problem to update our implementation for SAML V1.1.

 - irving -


-----------------------------------------------------------------------------------------------------------------
The information contained in this message is confidential and is intended
for the addressee(s) only.  If you have received this message in error or
there are any problems please notify the originator immediately.  The 
unauthorised use, disclosure, copying or alteration of this message is 
strictly forbidden. Baltimore Technologies plc will not be liable for
direct, special, indirect or consequential damages arising from alteration of the
contents of this message by a third party or as a result of any virus being 
passed on.
 
This footnote confirms that this email message has been swept for Content Security threats, including
computer viruses.

http://www.baltimore.com

 
This footnote confirms that this email message has been swept by 
Baltimore MIMEsweeper for Content Security threats, including
computer viruses.