SAML integration with AzureAD - Error when sent back to the GeoTab API

HomeCommunityMyGeotabLogging in & Getting startedSAML integration with AzureAD - Error when sent back to the GeoTab API

SAML integration with AzureAD - Error when sent back to the GeoTab API

Original Poster

Hi!

I've followed the "MyGeotab SAML 2.0 SSO Integration Guide" but even after reviewing everything multiple time, I cannot find the path to the solution.

Can somebody help me?

Here is the error I received from "https://my.geotab.com/apiv1/authenticateSaml?redirect=true" after login in correctly on AzureAD with a specific set of credentials for a user present in the GeoTab database. (The ID in the error message has been changed.)

{"error":{"message":"Incorrect login credentials","code":-32000,"data":{"id":"00000000-0000--0000--0000-000000000000","type":"InvalidUserException","requestIndex":0},"name":"JSONRPCError","errors":[{"message":"Incorrect login credentials","name":"InvalidUserException"}]},"jsonrpc":"2.0","requestIndex":0}

Here is some part of my configuration.

In AzureAD

In GeoTab:

Thank you!

Join the conversation

You need to be logged in to reply to this post and participate in the Geotab Community discussions.

3 Replies

LPPapillon-1145

You can use the SAML Tracer extension to debug the assertion going out to Geotab. The Issuer being sent by Azure AD must match what you set as the certificate name in Geotab to a T.

TuckerBA-1087

@David-1813

One other thing that could cause issues is if you're on a gov database. If so, you need to set up your urls to use gov.geotab.com instead of my.geotab.com. That was an issue one of our customers had, everything else was set up correctly, so if that applies to you, make sure you check that.

David-1813

Original Poster

Hi!

Thank you @LPPapillon-1145 and @TuckerBA-1087 for your quick feedbacks! Both ideas were on track.

As expected by the documentation (a bit complex to follow BTW), it turned out I didn't configure the claim correctly for the SSO configuration in Azure. I was copying the items Microsoft placed as the default claims and I was also integrating the Namespace schema instead of removing it. So once that was set, everything worked instantaneously!

Here is a screenshot of my final configuration.

Case closed! :)

Have a nice day!

Still have questions?

Learn with Academy Browse documents