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

Allow Data Connectors to release Attributes

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.0.0
    • Fix Version/s: 4.0.0
    • Component/s: Attribute Resolver
    • Labels:
      None

      Description

      An important motivation behind the transcoder work was to get away from having to have a specific encoder (and hence AttributeDefinition ) for every attribute release.

      In order for this to be useful we need to allow Data Connectors to "release" attributes directly - rather than the current mechanism in which they are only available as data dependencies.

      The user experience is

      • exportAttributes="Attribute Name List" or exportAllAttributes="boolean" added to the data connector.
      • Data Connectors add there attribute to the result bucket AFTER attribute resolution (may or may not be documented)
      • If we discover during attribute resolution that an attribute has already been defined (either by an attribute definition or by previous data connector resolution)
        • Issue a warning specifying the Data Connector and Attribute ID
        • Drop the data conector attribute
        • we might allow this to be turned into a failure
      • Attributes released from a data connector are not suitable for display (meaning consent flows)
        • They will have a autogenerated names in the "en" locale only.  Possible with warning text too.
      • As far the rest of the flows are concerned, these look just like attributes coming from an attribute definitions.  Specifically
        • Filtering
        • Any interaction with Requested Attributes (explicit or implicit)
        • Encoding

        Attachments

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 days
                2d
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 7 hours, 30 minutes Time Not Required
                7h 30m