Single Sign-On (SSO) and Other Login Troubleshooting
  • 21 Mar 2024
  • 4 minute read
  • Dark
    Light
  • PDF

Single Sign-On (SSO) and Other Login Troubleshooting

  • Dark
    Light
  • PDF

Article Summary

Error messages may be encountered using your single sign-on or SSO system during the login process. If you encounter an error not found below, please feel free to ask us in one of the three related community forums:

SAML Error: Unable to load metadata from remote server

Slate uses metadata hosted by your single sign-on to validate logins and allow access. This error means that the metadata is unable to be reached by Slate, and therefore you cannot log in. You will want to your with your IT colleagues to investigate why Slate cannot access your metadata.

Contact your identity provider or single sign-on system IT administrators for assistance. It's likely the metadata is unavailable due to the following:

  • A network outage

  • SSO or other campus system maintenance

  • A change in campus firewalls which are blocking Slate

  • The metadata has been removed and needs to be restored

Logins from this computer have been temporarily blocked

Slate tracks failed logins by IP address and temporarily blocks login attempts if too many failures have occurred recently. If you receive this error message, the best resolution is to wait a bit before logging in again. We recommend waiting 10-15 minutes at a minimum before attempting to log in again.

Logins to this account have been temporarily blocked

Slate tracks failed logins by account and temporarily blocks login attempts if too many failures have occurred recently. If you experience this error, we recommend you take a break for at least 10-15 minutes before attempting to log in again.

This browser does not appear to be configured to accept cookies

Slate uses cookies to authenticate your account into Slate properly. If you receive this error, Slate was previously unable to set the proper cookie. We recommend taking the following steps to correct this error.

  1. Verify your browser allows cookies to be set

  2. Clear your existing cookies/browser cache

  3. Exit and reopen your browser to start the login process from the beginning

VPN access required

Slate has been configured to limit access to specific campus networks. Please sign into your campus VPN before reattempting to log into Slate.

If you are logged into your campus VPN or are on campus, it is possible that your campus network addresses have been updated, and this change is not yet reflected in Slate. Please get in touch with your Slate Security Administrators to ensure all valid campus network addresses have been logged in Slate.

CAS Error: Unable to communicate with the authentication server

Slate authenticates CAS login requests against an institutional server and is presently unable to do so. You will want to your with your IT colleagues to investigate why Slate cannot access your CAS authentication server.

Contact your identity provider or single sign-on system IT administrators for assistance. It's likely the LDAP is unavailable due to...

  • A network outage

  • SSO or other campus system maintenance

  • A change in campus firewalls which are blocking Slate

  • A change in the authentication server URL or DNS entries

The account user_name is not authorized

The authentication against the SSO was successful, but the user does not have an account in Slate. Please get in touch with one of your Slate Security Administrators for assistance in granting access to Slate.

A supervised login is required for this account.

The authentication against the SSO was successful, but the user is configured to require supervision. A non-supervised account must log in first and provide the user with a login URL. Please see the Supervised setting in our Active User Settings article for more information.

LDAP Error: Unable to connect to LDAP service account

Slate's LDAP service account was unable to authenticate into the LDAP server.

Contact your campus IT administrators for assistance. LDAP is likely unavailable due to the following:

  • A network outage

  • SSO or other campus system maintenance

  • A change in campus firewalls which are blocking Slate

  • A change to the LDAP server IP address

  • The service account used by Slate to access the LDAP server has been removed or changed

If your campus IT needs to add Slate's IP addresses to the firewall to allow access to your LDAP server, those addresses are:

  • 34.197.57.115

  • 34.197.58.165

LDAP Error: Error Message Text

The text of the error message may vary here but will always be prefixed with "LDAP Error." This indicates that an error occurred when Slate attempted to contact your LDAP server, and you will need assistance from your campus IT staff for resolution.

Contact your campus IT administrators for assistance. LDAP is likely unavailable due to the following:

  • A network outage

  • SSO or other campus system maintenance

  • A change in campus firewalls which are blocking Slate

  • A change to the LDAP server IP address

If your campus IT needs to add Slate's IP addresses to the firewall to allow access to your LDAP server, those addresses are:

  • 34.197.57.115

  • 34.197.58.165

The application is not configured/The entity ID cannot be found

The text of this error message will vary depending on the provider and configuration but indicates that Slate is not yet allowed as an application in your identity provider. You will want to contact your SSO/IT administrators for assistance in configuring the SSO to allow Slate.

The user has no role/group for this application

The text of this error message will vary depending on the provider and configuration but indicates that the user attempting to access Slate is not allowed by the SSO. You must contact your SSO/IT administrators for assistance configuring the user on the SSO side for appropriate access to Slate.


Was this article helpful?