FIM- Import metadata with isDefault missing caused AttributeConsumingService to fail
Originally Published: 2008-06-24
Article Number
Applies To
Issue
Attributes are not passed in the session causing application to fail. None of the attributes are requested by the SP.
Cause
<md:AttributeConsumingService index="2">
Resolution
<md:AttributeConsumingService index="2" isDefault="true">
Notes
According to SAML spec:
At most one <md:AttributeConsumingService> element can have the attribute isDefault set to true.
When multiple elements are specified and none has the attribute isDefault set to true, then the first element whose isDefault attribute is not set to false is to be used as the default.
If all elements have their isDefault attribute set to false, then the first element is considered the default.
isDefault [Optional]
Identifies the default service supported by the service provider. Useful if the specific service is not otherwise indicated by application context. If omitted, the value is assumed to be false.
Related Articles
Problem importing metadata from into RSA FIM Number of Views RSA Governance & Lifecycle 7.5.2 Patch 1 Release Notes Number of Views Report Utility: Reports do not appear after being run from the command line Number of Views CreateChangeRequest webservice call with <AccountChange> does not fail on SoD Violations for RSA Via Lifecycle & Governance Number of Views RSA Identity Governance and Lifecycle - Purge monitor tasks Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process
Don't see what you're looking for?
