Uploaded image for project: 'Identity Provider'
  1. Identity Provider
  2. IDP-571

Names for attribute cause a Spring conflict with attribute identifiers

    XMLWordPrintable

    Details

      Description

      Consider a declaration:

      <resolver:AttributeDefinition id="skillsoftdept" xmlns="urn:mace:shibboleth:2.0:resolver:ad"
      xsi:type="Script"
      sourceAttributeID="uid">

      <resolver:Dependency ref="myLDAP" />

      <resolver:AttributeEncoder xsi:type="SAML2String" xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
      name="skillsoftdept"
      friendlyName="dept name for skillsoft"
      nameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified" />

      [Snip]
      </resolver:AttributeDefinition>

      The attribute never gets resolved - or even injected into the resolver. Changing the name of the AttributeEncoder to something other than the same name as the attribute solved the issue.

      This is a non-obvious problem since parsers instruct Spring to generate the id (shouldGenerateId is returns true).

        Attachments

          Activity

            People

            Assignee:
            rdw@iay.org.uk Rod Widdowson
            Reporter:
            rdw@iay.org.uk Rod Widdowson
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 5 hours Original Estimate - 5 hours
                5h
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 5 hours, 31 minutes
                5h 31m