No internet connection
  1. Home
  2. Questions

OAuth SignIn to Microsoft Graph

By David @Unica2021-04-15 13:47:54.741Z

One of the issues I have encountered is this error when using the OAuth SignIn action:

The fields that we filled in:

Authorization Endpoint: https://login.microsoftonline.com/{tenantId}/oauth2/v2.0/authorize
Token Endpoint https://login.microsoftonline.com/{tenantId}/oauth2/v2.0/token
ClientID: is the application ID from Microsoft
Client Secret: is the secret from Microsoft
Scope: https://graph.microsoft.com/Files.ReadWrite.All https://graph.microsoft.com/User.Read https://graph.microsoft.com/.default

Whatever I fill-in, I keep on getting the same error.

  • 7 replies
  1. Ollie A @olliea2021-04-20 10:40:51.895Z

    Hello David,

    From what I understand this is a current issue that is being worked on by our development team, and it sounds like this will hopefully be resolved in the next update although I can't say when that will be.

    I will let you know as soon as I can, when I have either more information or an update is released which addresses the issue.

    1. Ollie A @olliea2021-04-20 13:52:15.785Z

      Hello David @Unica, it looks like version 5.0.556.2 has resolved this issue, however the latest as of 14:51 BST is version 5.0.557.2, so please update when convenient, and apologies for any inconvenience or disruption.

      1. UDavid @Unica2021-04-21 13:17:40.784Z

        Great work, we are progressing. Could you help me out with just one more thing: the ‘Reply URL’ / ‘Redirect URI’ TA5 is using.

        1. Thomas Parker @mrtopkid2021-05-05 17:39:04.423Z

          Hi David,

          I'm not sure I fully understand the query :(

          Could you describe the question a little more for me please? I'll do my best to help.

          1. UDavid @Unica2021-05-05 18:42:43.746Z

            Would the error message help?

            1. LLiam @liam2021-05-12 09:33:25.351Z

              Hi David

              What version of TA5 are you now running?
              However, we think the issue is probably going to be the callback URL port not matching the redirect URI that is set up within your azure app.
              Within Azure

              The setting within TA5

              1. UDavid @Unica2021-05-12 10:35:50.180Z

                Liam, thank you. I have sent additional info and screenshots to Benjamin Wilshaw.