Gayathri Vijayan 00b0af4368 fix(saml): use transient mapping attribute when nameID is missing in saml response (#10353) ...

# Which Problems Are Solved

In the SAML responses from some IDPs (e.g. ADFS and Shibboleth), the
`<NameID>` part could be missing in `<Subject>`, and in some cases, the
`<Subject>` part might be missing as well. This causes Zitadel to fail
the SAML login with the following error message:

```
ID=SAML-EFG32 Message=Errors.Intent.ResponseInvalid
```

# How the Problems Are Solved

This is solved by adding a workaround to accept a transient mapping
attribute when the `NameID` or the `Subject` is missing in the SAML
response. This requires setting the custom transient mapping attribute
in the SAML IDP config in Zitadel, and it should be present in the SAML
response as well.

<img width="639" height="173" alt="image"
src="https://github.com/user-attachments/assets/cbb792f1-aa6c-4b16-ad31-bd126d164eae"
/>


# Additional Changes
N/A

# Additional Context
- Closes #10251

2025-07-31 15:12:26 +00:00

..

providers

fix(saml): use transient mapping attribute when nameID is missing in saml response (#10353)

2025-07-31 15:12:26 +00:00

provider.go

fix: improve login_hint usage on IDPs (#6899)

2023-11-13 09:25:26 +01:00

session.go

fix(api): return typed saml form post data in idp intent (#10136)

2025-06-30 15:07:33 +00:00