OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

security-services-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Change in saml-schema-assertion-2.0.xsd for NET1.1


Hello

I'm implementing SAML in my NET1.1 application and I had an issue with

 the SubjectConfirmationDataType type.

 

The original definition is:

and when I run xsd.exe (NET1.1) it generates the class as:

 

SubjectConfirmationDataType

{

     string[] Text;

}

 

But when I change it as (without complexContent):

 

 

The class gets generated correctly:

       public class SubjectConfirmationDataType {

 

           ///

           [System.Xml.Serialization.XmlAttributeAttribute()]

           public System.DateTime NotBefore;

 

           ///

           [System.Xml.Serialization.XmlIgnoreAttribute()]

           public bool NotBeforeSpecified;

 

           ///

           [System.Xml.Serialization.XmlAttributeAttribute()]

           public System.DateTime NotOnOrAfter;

 

           ///

           [System.Xml.Serialization.XmlIgnoreAttribute()]

           public bool NotOnOrAfterSpecified;

 

           ///

 

[System.Xml.Serialization.XmlAttributeAttribute(DataType="anyURI")]

           public string Recipient;

 

           ///

 

[System.Xml.Serialization.XmlAttributeAttribute(DataType="NCName")]

           public string InResponseTo;

 

           ///

           [System.Xml.Serialization.XmlAttributeAttribute()]

           public string Address;

 

           ///

           [System.Xml.Serialization.XmlTextAttribute()]

           public string[] Text;

       }

 

Can this be introduced as an update to the official SAML2.0 schema?

 

I understand that this may be an issue in the xsd.exe.

BUT I still think the schema could be simplified so all technologies

 are supported equally (maybe not how I did it, but there is something funky

in that definition that does not work in NET1.1).

 

Thanks



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]