As a workaround, I found that if I load the User object from the Management API, rather than rely on the User object I receive within the Event parameter, I am able to see claims, such as groups, that were added from the SAML token. I hope this helps!
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Actions not working for SAML2 application settings (mapping) as rules | 2 | 1234 | February 22, 2024 | |
| Mapping Extra SAML Attributes to App Metadata | 2 | 2172 | August 29, 2023 | |
| Read SAML Response Claims from IdPs inside Actions | 7 | 2712 | January 12, 2024 | |
| Map SAML attributes to user_metadata attributes via action | 3 | 2063 | September 26, 2024 | |
| Unlocking more customization in Actions with three new capabilities | 8 | 3862 | April 9, 2024 |