Behaviour change between IS 5.10.0 - IS 7.2.0 on IDP claim mapping

[DilshaniSH]

Description

In IS 5.10.0, when a SAML federation flow is configured and the external SAML IdP returns a set of user attributes, the federated claims are passed to the SP and included in the ID token even when no claim mappings are configured under the IdP configuration.

However, in IS 7.2.0, this behavior has changed. Claims received from the external SAML IdP are passed into the ID token only if explicit claim mappings are present in the IdP configuration, mapping the external claims to local claims. Without such mappings, none of the federated claims are included in the ID token.

Steps to Reproduce

1. Configure a saml federation flow in IS 5.10.0 and make sure set of custom claims are returned by the external IDP.
2. Confirm that these custom claim values present in the ID token without any claim mappings under the IDP or SP.
3. Migrate to IS 7.2.0 and test the same federation flow.
4. Custom claims are not included in the token.

Please select the area issue is related to

Other

Version

IS 7.2.0

Environment Details (with versions)

No response

Developer Checklist

• [Behavioural Change] Does this change introduce a behavioral change to the product?
•  ↳ Approved by team lead
•  ↳ Label impact/behavioral-change added
• [Migration Impact] Does this change have a migration impact?
•  ↳ Migration label added (e.g., 7.2.0-migration)
•  ↳ Migration issues created and linked
• [New Configuration] Does this change introduce a new configuration?
•  ↳ Label config added
•  ↳ Configuration is properly documented