Lattice can integrate with any SAML 2.0 identity provider. Some common SSO providers of Lattice customers include Google, Okta, and OneLogin. If you’re running into issues, you’ll want to follow the below steps.
For Lattice Users:
- Reach out to your Admin to make sure you're on the correct wifi.
- Contact your internal IT/Lattice Admin team to share any error messages.
- If possible, try logging in directly with your email address and password.
- If you’re having trouble configuring SSO for your company, we recommend that your IT team assist with set up. Please reach out to them for help.
- Make sure that you’ve enabled Lattice for the particular user within your SSO provider. In other words, not only do you need to add Lattice to Okta, but you need to add Lattice users to Okta as well.
- If an individual or specific group of employees is having trouble logging in, you’ll want to make sure that the email address(es) that they’re trying to log in with (have been provisioned in your SSO) is the same as their email in Lattice.
- Verify your ACS URL. It should be the unique part of your Lattice domain (i.e. "lattice" not "www.lattice.latticehq.com"). Incorrect ACS URLs may result in errors including, "Cannot POST" and "Not Found".
- If all else fails, try re-uploading your XML Metadata (if you've made changes to the force login settings, this may be a necessary requirement).
For Google: If you see the below error message, it means you may have accidentally added a space before or after your ACS URL.