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
Report Utility: Reports do not appear after being run from the command line Number of Views Problem importing metadata from into RSA FIM Number of Views Checkboxes do not work correctly on the Import/Export Metadata page in RSA Identity Governance & Lifecycle Number of Views Remote agent fails to start after metadata import Number of Views Form Control Type 'User Picker' with the User filter option generates a SQL Exception in RSA Identity Governance & Lifecycle Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?
