Now that geotab supports OAuth is it to early to add it to our integrations. I have smoke tested a Geotab OAuth Credential Type in our current integration. Do you plan on having OAuth being a documented method for integrations. Is it fine to use in production or should I hold out.
You need to be logged in to reply to this post and participate in the Geotab Community discussions.
Hey @shanegraham ,
Thank you for asking your question in our community. I wanted to let you know I have contacted our SDK team to get them to weigh in on this I will let you know what I hear as soon as I do.
Feel free to reach out if you have any other questions in the meantime. We are here to help.
Have a great day!
Eishi FUN
Hey @shanegraham I wanted to follow up with you on this question after I talked with our SDK team about this.
OAuth is a known direction for MyGeotab integrations, and the team intends to document and officially support it for public use. However, that work is not complete yet, and there is currently no confirmed timeline for when the public documentation and supporting automation will be available.
Because of that, I would treat the OAuth credential type as experimental for now. It may work in production if you have already configured and tested it successfully, but it is not yet an officially documented or supported integration path. There is also a possibility that the current implementation could change before the supported public version is released.
If your integration requires a fully supported production authentication method, I would recommend holding off for now or continuing to use the currently documented authentication approach.
Hope that helps!
Eishi FUN
@EishiFUN Thank you for the follow up. We have successfully added Geotabs OAuth to our mg-api-js wrapper for when the time comes but for now we will continue to run service accounts untillit hits the public documentation.