Make SupportedClaimTypeList optional

XMLWordPrintable

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Affects Version/s: IMI 1.1 CD1
    • Component/s: Schema, Spec
    • None
    • Hide

      Add minOccurs=0 to SupportedClaimTypeList in InformationCardType:

      <xs:complexType name="InformationCardType">
      <xs:sequence>
      <xs:element ref="tns:InformationCardReference" />
      <xs:element ref="tns:CardName" minOccurs="0" />
      <xs:element ref="tns:CardImage" minOccurs="0" />
      <xs:element ref="tns:Issuer" />
      <xs:element ref="tns:TimeIssued" />
      <xs:element ref="tns:TimeExpires" minOccurs="0" />
      <xs:element ref="tns:TokenServiceList" minOccurs="0"/>
      <xs:element ref="tns:SupportedTokenTypeList" />
      <xs:element ref="tns:SupportedClaimTypeList" minOccurs="0"/>
      <xs:element ref="tns:RequireAppliesTo" minOccurs="0" />
      <xs:element ref="tns:PrivacyNotice" minOccurs="0" />
      <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
      </xs:sequence>
      <xs:attribute ref="xml:lang" use="required"/>
      </xs:complexType>

      Change the spec that in the case when SupportedClaimTypeList is missing in the card then the MetaData section in all EndpointReferenceType definitions MUST not be missing and the retrieved metadata must specify the supported claims; else there would be no way for the selector to decide whether a card resp. the IdP can provide the required claims.

      Can one specify the supported claims in the current version of meta data?

      Show
      Add minOccurs=0 to SupportedClaimTypeList in InformationCardType: <xs:complexType name="InformationCardType"> <xs:sequence> <xs:element ref="tns:InformationCardReference" /> <xs:element ref="tns:CardName" minOccurs="0" /> <xs:element ref="tns:CardImage" minOccurs="0" /> <xs:element ref="tns:Issuer" /> <xs:element ref="tns:TimeIssued" /> <xs:element ref="tns:TimeExpires" minOccurs="0" /> <xs:element ref="tns:TokenServiceList" minOccurs="0"/> <xs:element ref="tns:SupportedTokenTypeList" /> <xs:element ref="tns:SupportedClaimTypeList" minOccurs="0"/> <xs:element ref="tns:RequireAppliesTo" minOccurs="0" /> <xs:element ref="tns:PrivacyNotice" minOccurs="0" /> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute ref="xml:lang" use="required"/> </xs:complexType> Change the spec that in the case when SupportedClaimTypeList is missing in the card then the MetaData section in all EndpointReferenceType definitions MUST not be missing and the retrieved metadata must specify the supported claims; else there would be no way for the selector to decide whether a card resp. the IdP can provide the required claims. Can one specify the supported claims in the current version of meta data?

      Do we need SupportedClaimType or should that become optional?
      That would imply that the selector fetches equivalent metadata from the IdP from time to time.

      Following is the current definition:
      <xs:complexType name="InformationCardType">
      <xs:sequence>
      <xs:element ref="tns:InformationCardReference" />
      <xs:element ref="tns:CardName" minOccurs="0" />
      <xs:element ref="tns:CardImage" minOccurs="0" />
      <xs:element ref="tns:Issuer" />
      <xs:element ref="tns:TimeIssued" />
      <xs:element ref="tns:TimeExpires" minOccurs="0" />
      <xs:element ref="tns:TokenServiceList" minOccurs="0"/>
      <xs:element ref="tns:SupportedTokenTypeList" />
      <xs:element ref="tns:SupportedClaimTypeList" />
      <xs:element ref="tns:RequireAppliesTo" minOccurs="0" />
      <xs:element ref="tns:PrivacyNotice" minOccurs="0" />
      <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
      </xs:sequence>
      <xs:attribute ref="xml:lang" use="required"/>
      </xs:complexType>

            Assignee:
            Unassigned
            Reporter:
            Axel Nennker (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: