Access and SSO

The questions below cover the most common causes of login errors, including error pages when you try to access Amplitude and 500 or 403 errors after authenticating with SSO.

What do I do if I'm having an issue logging in with a password?

Try each of these steps:

Confirm the password is correct. Reset it if you've forgotten.
Check whether the same problem happens in another browser or in incognito mode. If not, clear your browser's cookies and cache.
Make sure your browser is up to date. Restart your laptop after updating to make sure the browser fully relaunches, and try again.
Confirm your browser is supported. Refer to browser compatibility.
Disable ad blockers and VPNs, or add Amplitude to their allowed list. Ad blockers and VPNs can cause Amplitude to behave unexpectedly.
If you've forgotten your organization's URL, reach out to Amplitude support. They can tell you which organization is associated with your email address.

How do I fix a problem with logging in by SSO?

A common SSO error is a 500 internal server error. A 500 error usually means a problem with your SAML certificate, and the problem can affect every user in your organization. To resolve the error:

You need access to the Amplitude platform to upload a new certificate. If you need to disable SSO to log in and fix the problem, contact the Support team.
Check with your IT team to confirm whether the SAML certificate has expired. If it has, upload a new one.
Confirm the SAML certificate uses the correct format. If not, an Amplitude admin should upload a correctly formatted certificate.

If you've configured SSO through Google Workspace, you might see 403 Error: app_not_enabled_for_user or 403 Error: app_not_configured_for_user.

To resolve this error, follow Google Workspace Admin Help for step-by-step instructions.

If these tips don't fix the problem, contact Amplitude support. Include the browser you're using, plus its version, in your request.

Was this helpful?