Single sign-on (SSO) login overview

It ensures secure and efficient access to TomTom products and services, as well as easy user management that accommodates changes in your team. This is the preferred option for professional developers working in enterprises and in teams with multiple developers who need access to TomTom services for production or evaluation purposes.

To see how to request and manage access using SSO in practice, see Managing access with single sign-on (SSO).
How does SSO work?
Each user at your company can authenticate in a TomTom application using their company credentials. Once successfully authenticated, the user can access TomTom products and services without needing to log in again, based on their granted access permissions. As user identity is verified by your company’s authentication service (identity provider), TomTom does not store any login credentials related to the user.
Access to the assets provisioned to your company by TomTom is managed by an approver designated within your organization.
Here is a diagram showing the process:

→ Open TomTom application
← Redirect to login
↔ Sign-in user or redirect to TomTom authentication service
↔ Verify user’s identity at the customer’s identity provider and store authentication cookie
↔ If user is logged out, sign in again at the customer’s identity provider and store authentication cookie
→ Send authentication data
↔ Verify authentication data
← Load TomTom application content