Troubleshooting login and password issues

Diagnose and resolve common issues with logging in, setting passwords, and authenticating with the Altitude platform.

Setting a password from the welcome email

When an administrator adds a new user to a database, Altitude sends a welcome email containing the database name, server address, and a link to set an initial password.

To set a password:

  1. Open the welcome email and click Click here to open the password setup page.
    Important:

    The welcome email also displays the portal URL as a reference. Do not copy and navigate to this URL directly. It opens the login page, not the password setup page. Use the Click here button only.

  2. Enter and confirm a password, then save.
  3. Log in at Altitude using the email address and the password that was just set.

If the welcome email has expired or the link no longer works, an administrator can remove and re-add the user account. This generates a new welcome email with a fresh password setup link.

Password reset not working

Password resets are scoped to a specific database. Resetting a password in one database does not grant access to a different database. The user must be added to each database individually by an administrator.

Common reasons a password reset does not work:

  • Account lockout: Too many failed login attempts lock the account before a reset can be completed. Contact a database administrator to unlock the account, then request a new reset email.
  • Reset link redirects to the login page: A known intermittent issue causes reset emails to link to the login page instead of the password setup page. If this occurs, an administrator can reset the password manually from User Management, or remove and re-add the user to generate a new welcome email.
  • Reset email not received: Check the spam or junk folder. If the email is not there, an administrator can resend the reset from User Management. If the issue persists, removing and re-adding the user sends a new welcome email through a different delivery path.

For information on sending a password reset from User Management, refer to Resetting a password.

"Incorrect sign in credentials" error

The Incorrect sign in credentials error appears when the email address, password, or server name does not match the account record. Check the following:

  • Email address: Use the exact email address from the welcome email. Email addresses are case-insensitive, but verify there are no extra spaces or typos.
  • Server name: Use altitude.geotab.com unless the welcome email specifies a different server. Avoid appending a number (for example, altitude1.geotab.com) unless explicitly directed.
  • Password: If the password was set recently, confirm it matches exactly. If unsure, request a password reset from a database administrator.
  • Account lockout: Repeated failed login attempts lock the account. A database administrator can unlock it from User Management.

Geotab SSO users unable to access a database

Geotab employees who authenticate using Geotab single sign-on (SSO) must be explicitly added to each database before they can log in. SSO does not automatically grant access to all databases. A database administrator must add the SSO user's email address through User Management in the target database.

API requests are rejected with an authentication error

API requests are authenticated with an API key that is sent in the Authorization header. A request with a missing or invalid key is rejected with a 401 response.

To resolve the error:

  1. Confirm that every request includes the header Authorization: Bearer <your-api-key>. For a complete example request, refer to Making an API Request with a POST Request.
  2. Confirm that the full key was copied, with no missing characters or extra spaces.
  3. If the key was lost or might be incorrect, generate a new key and use it in your requests. An API key is shown only once, when it is generated. For the steps, refer to Getting Altitude Credentials.

Unable to log in to a trial or expired database

Trial databases have a fixed expiry date. After a database expires, the Incorrect sign in credentials error may appear at login, or a message stating the database has expired appears after authentication succeeds. In either case, access to the expired database cannot be restored without a license renewal.

Contact the Altitude support team to confirm whether a database has expired and to discuss renewal or migration to an active database.

When to contact support

Contact the Altitude support team when:

  • The password reset redirect issue persists after an administrator has attempted a manual reset and a remove-and-re-add.
  • The SSO user has been added to the database but still cannot log in.
  • The database has expired and renewal or migration is needed.
  • An account is locked and no database administrator is available to unlock it.

When contacting support, provide the affected email address, the database name, the server address from the welcome email, and a description of the error message received.

For API errors, also provide the requestId from the error response, or the X-Request-ID response header. It identifies the failed request.