We use SSO via SAML 2.0 for Knack. Because I do not know a way around creating a user in the Roles table without having to give them a password, I resulted to setting up a form inside the app where administrators can create the user into that table without the password field. This allows them to login and be authenticated against our SSO. Is this really the best way to handle this? I ask because I need to add about 120 people and having to do that one-by-one will be painful versus being able to just mass import users. Should I use the standard Roles table import the individuals and give it a password even though they do not have the option to use the username and password fields when logging into the application only the SSO button?
So the answer here is yes. Just use the Builder import and set a common default password which is some very long random string of letters numbers and symbols that even you don’t remember.
Even if you still allow direct logins for other external users, the chances of anyone in your SSO cohort cracking that are very low and it gets past the mandatory password issue.
But you would have to hide the Forgot Password link …
1 Like
Thanks I wish they would call special attention to “Best Practices” in the guide especially for SSO users. They really just leave us hanging a lot.