When connecting via SSO and adding a display name, a password field appears "intermittently."
Background
As a user types in the Name field, Vanilla performs a lookup to see if that name exists in the community. If it does, it's assumed that the user who is typing is the same user who created the account; the password field then displays, giving them an opportunity to enter a password and log in.
The password field will only display if:
- A user types in a name that exists in the system.
- A user types slowly enough so the system can display a partial match. If the user keeps typing and the name no longer has a match, the password field is hidden.
Workaround
🛑 IMPORTANT: This workaround only works if you have your SSO set to AutoConnect users.
In other words, if the email being passed over in the SSO response matches the email of an existing account in the community, you trust that it's the same user and you automatically connect them. In this case, you're only presenting the password field for the purpose of connecting user names.
📝 NOTE: For more on AutoConnect, check out this article.
To change this behaviour, you can override the CSS by adding this line to either your custom CSS or in a Pocket in the Dashboard:
#ConnectPassword {
display: none !important;
}
The !important is essential because JavaScript is injecting an in-line style to display it. This will ensure that this declaration is given priority.
If you find that you're receiving a "Password required" error but there is no Password field, it's because you have implemented this workaround without having your SSO Registration set to AutoConnect.