2

I am currently working on the redesign of SSO signup process/form and want to understand what enabling SAML control implies.

The rationale being that if an organisation does not have SSO enabled the user will be prompted to signup by imputing required details and following the process through rather than enabling first and then inputting the details. Am I missing something here? Is this a backend requirement?

Here is a screenshot: enter image description here

Note: I understand what SAML is, just don't understand why there is a UI control/switch for it (TickBox). Is this not adding an unnecessary step to the workflow?

1 Answer 1

3

As you already know what SAML is, I'm not going to go into specifics of that and simply consider it a system for federated sign-ups / log-ins.

What you've shows seems to be a simple option as to whether the application should use a federated sign-on or not. Some organisations prefer to have all the login and security information for a user stored locally, and in those situations they wouldn't enable federated sign-ups.

Take this site for example. When you sign-up for an account you have three options. Two are federated sign-ups, and one is internal.

enter image description here

If you were to have a setup for some software like this site, and you chose not to use a federated sign-up, you would end up with only the one option, and the sign-up would look like this:

enter image description here

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.