Deane Sloan
2006-07-21 14:32:36 UTC
Hi,
When integrating with a commercial SAML 1.1 asserting party, we encountered
issues with the RequestID generated by
SourceID.SamlSupport.DocumentSignatureSupport:GenerateNewID().
The GenerateID function doesn't seem to follow the XML ID/NCName production
rules, resulting in IDs containing the ':' character. We also experienced
issues when IDs were generated with a leading digit (prohibited by the
'Name' production rules also?).
Easily solved and I'm not sure if this is an implementation fault or simply
an interop issue - however it might also catch other users of this useful
toolkit.
Thanks,
Deane
When integrating with a commercial SAML 1.1 asserting party, we encountered
issues with the RequestID generated by
SourceID.SamlSupport.DocumentSignatureSupport:GenerateNewID().
The GenerateID function doesn't seem to follow the XML ID/NCName production
rules, resulting in IDs containing the ':' character. We also experienced
issues when IDs were generated with a leading digit (prohibited by the
'Name' production rules also?).
Easily solved and I'm not sure if this is an implementation fault or simply
an interop issue - however it might also catch other users of this useful
toolkit.
Thanks,
Deane