When our server tries to create a new Geotab user it receives an error from Geotab API that username cannot be email but Geotab API has only a single field for User and we cannot assign 2 different values for the username and email. There doesn't appear to be an changes to the current API or a new API.
We do not have this error for old companies but for some new companies we have this error.
You need to be logged in to reply to this post and participate in the Geotab Community discussions.
Hey @eiler-6441 ,
Hi, great question and one that is worth investigating properly. I think I know what is going on here based on some recent changed with MyGeotab logins.
What you are probably experiencing is related to the Unified Login rollout which is a centralized identity platform that new databases are now on by default. Older databases use a legacy per-database authentication model where the username and email were effectively the same field, but new databases on Unified Login enforce a separation between the local username and the email identity.
This change is what is causing the inconsistency you are seeing between old and new companies.
For integrators creating users via the API against new databases, the handling is different and the current documentation may not fully reflect this yet. I would recommend:
1. Reviewing the Unified Login overview (https://support.geotab.com/help/mygeotab/access-and-administration/log-ins/unified-login-overview) for context on how the new identity model works
2. Opening a support ticket so our team can advise on the correct API approach for creating users on Unified Login databases — this is a technical integration question that needs specific guidance
We want to make sure this is properly documented for developers. Thank you for flagging it.
Have a great day!
Eishi FUN
Hey @eiler-6441 ,
Hi, great question and one that is worth investigating properly. I think I know what is going on here based on some recent changed with MyGeotab logins.
What you are probably experiencing is related to the Unified Login rollout which is a centralized identity platform that new databases are now on by default. Older databases use a legacy per-database authentication model where the username and email were effectively the same field, but new databases on Unified Login enforce a separation between the local username and the email identity.
This change is what is causing the inconsistency you are seeing between old and new companies.
For integrators creating users via the API against new databases, the handling is different and the current documentation may not fully reflect this yet. I would recommend:
1. Reviewing the Unified Login overview (https://support.geotab.com/help/mygeotab/access-and-administration/log-ins/unified-login-overview) for context on how the new identity model works
2. Opening a support ticket so our team can advise on the correct API approach for creating users on Unified Login databases — this is a technical integration question that needs specific guidance
We want to make sure this is properly documented for developers. Thank you for flagging it.
Have a great day!
Eishi FUN