What is an enterprise login?
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.
How does enterprise login work?
Each user at your company can authenticate in TomTom Developer Portal using your own company credentials. Once successfully authenticated, the user can access TomTom products and services without a need to re-login based on their granted access permissions. As user identity is verified by your own company’s authentication service (Identity Provider), TomTom does not need to store any login credentials related to the user.
The actual access to the assets provisioned to your company by TomTom is managed by an Approver established in your company.
Here is a short diagram showing the processes:
→ Open TomTom Application
← Redirect to Login
Sign-in User or redirect to TomTom Authentication Service
Verify User’s identity at Customer’s Identity Provider and store authentication cookie
If User is logged out, sign in User at Customer’s Identity Provider and store authentication cookie
→ Send authentication data
Verify authentication data
← Load TomTom Application content
What user roles are supported?
| Approver | User |
|---|---|
| A role dedicated to individuals responsible for managing the company’s account in TomTom, configuring API Keys and managing the accessi to TomTom applications. | A role dedicated to individual Developers and other users in your Company who need Developer Portal and/or other TomTom applications in their regular work. |
Approver key permissions:
Change API key configuration.
Add, delete, rotate API keys.
Request change of QPS (quota per second)
View usage analytics information.
User key permissions:
Use the API keys enabled with the access package
Display the API key configuration
View usage analytics information.
What are the conditions to enable Enterprise login?
| Technical | Organizational |
|---|---|
| No time-consuming alignments between IT departments. | No overhead to manage the company’s enterprise account. |
| TomTom establishes SSO based on your company’s domain. | |
| Your company identifies two users for Approver role per each contract signed with TomTom. | |
| Approver will manage the user access to TomTom resources. |
Each user in your company needs to onboard:
Grant access permission for TomTom to (a) read the name, e-mail, and photo; (b) process the data to create, control, and administer the account in TomTom Azure AD according to TomTom policy.
Accept online service Terms of Use
Configure Multi-Factor Authentication.
How can I start using Enterprise login?
Important: Your company must be enabled to use the TomTom enterprise login first before you start onboarding.
Self-onboard by running the following steps:Open TomTom My Access Portal.
- Sign in using your company username and password.
- If needed, request access to the TomTom resources provisioned to your company. To do so, follow the steps below:
Select an access package from the list and click the Request action.
Note: Check with your Approver which package serves best for your project.
Provide business justification and submit the request by clicking on Request access.
Note: The Approver established at your company will receive a notification about your request and can approve it to grant and access permission for you.
- Await request approval by your Approver. We will provide you with access as soon as possible after approval.
Note: Be patient as provisioning might take more than an hour.
Go to https://myapps.microsoft.com/.
- Click the organization chart on the right side of the page and choose TomTom organization.
- Accept the Terms of Use.
- If prompted, set up your multi-factor authentication (MFA) option (Authenticator app is set by default).
How can I log in to my company enterprise account?
- Developer Portal login screen and select “Enterprise login” option.
- Type your company email address.
- If needed, provide additional information requested for authentication, such as your password and multi-factor authentication data.
What do I do if my e-mail address does not work?
Check if your e-mail address was entered correctly and retry.
- If your company uses multiple versions of e-mail addresses (formal or alias), ensure the address you entered comes from the domain provided to TomTom for SSO integration (check with your Approver).
Report the TomTom Developer Relations team using this email: developerrelations@tomtom.com.
What do I do if I do not see production API keys?
- Follow the procedure: How to request access to the new app or service?
- Be patient as the provisioning access can take more than an hour.
Report the Developer Support case and provide “SSO – don’t see my production API Key” in the summary field.