Skip to main content
B
behinjebarsond9891
May 12, 2026
Question

Cannot request SAML Assertion for SBAF Authorize Click since user is not valid for SBAF

  • May 12, 2026
  • 2 replies
  • 0 views

When user logs in using SAML, they face 403 access denied error. We checked the users ID and they have the required access levels. When checked on tomcat-stdout logs we see the following issue 'Cannot request SAML Assertion for SBAF Authorize Click since user is not valid for SBAF'. Any leads on this?

2 replies

shubhama926776
shubhama926776
May 12, 2026

Is this user logging in for the first time, or did it work before and suddenly broke?
Still you can check few basic things :-
Check user is active and should be part of SAML Users/authentication group.
Verify the IdP is sending the exact Appian username, with correct case.
If group sync enabled, confirm user is in auth group prior to SAML login, as sync happens post-auth.

FYI - https://community.appian.com/support/w/kb/370/kb-1153-saml-authentication-faq

gayathris111098
gayathris111098
May 12, 2026

Run a SAML Trace, capture exactly what the IdP is sending. The KB article KB-1450 specifically covers how to gather a SAML trace to identify the Appian username shown in the SAML assertion — this will tell you definitively what value SBAF is trying to validate against. Appian


Terms & ConditionsAccessibility statement