...
| Warning |
|---|
This is not a replacement for the actual documentation and you cannot cut and paste your way to a working system. The examples are not usable without taking into consideration your local needs and requirements. |
...
Example Shibboleth Configuration
| Tip |
|---|
Refer to the RelyingPartyConfiguration topic and be cognizant that creating overrides for every service is generally an inefficient use of the software. Consider identifying common requirements across services and create overrides tied to multiple services that share those requirements, or that reference profile configuration beans containing common settings. |
...
Example Shibboleth Configuration
| Tip |
|---|
Refer to the NameIDGenerationConfiguration topic for a full treatment of NameID features. |
Continuing with the example above, if you have an attribute definition named "mail" produced by your AttributeResolverConfiguration, release it to the Datadog in your AttributeFilterConfiguration (example below).
Finally, to actually produce the necessary <NameID>, modify saml-nameid.xml as shown:
...
Datadog does not appear to support attributes for login, but it may rely on them for just-in-time priovisioningprovisioning, don't know for certain. That might explain the metadata claiming to support the standard attributes for first and last name, but wouldn't explain the reference to eduPersonPrincipalName, since that certainly isn't the same as requiring an email address.
...