SSO URL Fields should not accept whitespaces
Closed this issue · 0 comments
sebastian-bury commented
Describe the bug
Entity ID, Single Sign-On URL, Discover URL, etc. should not accept whitespace.
Today spent a decent amount of time debugging with a customer on why their SSO wasn't working, including involving the Unleash platform team to dive into logs and find the issue. The issue was a leading whitespace on the Entity ID, this meant the user was able to click 'Sign in with SAML 2.0', Azure saw a successful attempt, and Unleash then failed to log the user in.
Whitespaces should either be trimmed or give a warning to the user that they might not want to have it there.
Steps to reproduce the bug
No response
Expected behavior
No response
Logs, error output, etc.
No response
Screenshots
No response
Additional context
No response
Unleash version
No response
Subscription type
None
Hosting type
None
SDK information (language and version)
No response