Hi On Wed, 6 Jul 2011, John MacAuley wrote:
7. Modified all security attributes to use the saml:attribute element as per Mary's security proposal. Now import http://docs.oasis-open.org/security/saml/v2.0/saml-schema-assertion-2.0.xsd. Created the SubjectAttributeSequenceType to hold these attributes.
Hmm... this pulls in http://docs.oasis-open.org/security/saml/v2.0/saml-schema-assertion-2.0.xsd which again pulls http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd Which is a dead link. This causes my client to hang, and crash after a timeout. This might be the client which does not know about xmldsig magic, or an error in the schema, but I don't think we should have a schema which links to something which does not exist (I doubt my client is the only library which has this behaviour). Also it seems the default link has switched to https (which is good), but I find usage of TLS AND SAML at the same time to be a bit odd. Best regards, Henrik Henrik Thostrup Jensen <htj at ndgf.org> NORDUnet / Nordic Data Grid Facility.