Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Attribute Mappers (or decoders)

Warning

This section is now of historic nterest only.

These functions are now performanced by the Attribute Registry

The Attribute Mapper is the inverse of attribute encoding.  These components inspect metadata (usually of the SP) to extract any SAML2 RequestedAttributes.  These are decoded use the same configuration as the attribute encoders to produce  IdPRequestedAttribute. This decoding includes not only the name changes (from the on-the-wire names to those used to configure the Attribute Resolver and Filter), but also types, as defined by the Attribute Encoders.

...

So, what actually happens when the resolver runs? How do all of these components fit together? The attribute resolution process goes like this:

  • Prerequested Attributes (TBD)

For each defined attribute definition:

...

  • if any dependency is listed, and has not yet been executed, it is executed
  • if no evaluation condition is given or a condition is given and it evaluates to true then proceed
  • the data connector is executed
  • TBD exportAttributes will create the output attributes
  • the results of the execution are cached for the current request

...