Attribute Release Not Working
Cantor, Scott
cantor.2 at osu.edu
Mon Jul 14 12:32:40 UTC 2025
> The docs gave me the impression that I just needed to do
> exportAttributes="sAMAccountName" and <AttributeRule
> attributeID="sAMAccountName" permitAny="true"/> but there is
> simply no AttributeStatement in the SAMLResponse.
Because there's no encoder to apply, the log will tell you that explicitly later on when it's building the response.
Exporting something from a DataConnector only works if there's a definition for it in the transcoding registry service (the dictionary of rules for how to name things).
Absent that, you'd have to define a Simple AttributeDefinition to be able to add an AttributeEncoder (the legacy way we used to name attributes) and feed the resolver file into the registry service's list of resources to construct an encoding rule based on it.
One reason for this is to make it more painful to do things you shouldn't do, and using sAMAccountName for anything is a good "anti-pattern" example of that, that's not a standard federated attribute.
-- Scott
More information about the users
mailing list