Hi,

Is there any way to get more specific information about the reason behind an "invalid_client" message when trying to setup Microsoft OAuth2 authorization for a user. I have followed the new setup instructions and so far no luck getting it to work.

Thanks,
Charlotte

  • KevinTheJedi replied to this.

  • I had this issue, only to find out you need to use the value of your client secret instead of the Secret ID.

    mcclell

    You can inspect the page, go to the network tab, and then make the request. Typically it'll throw a URL with the error message in it.

    Cheers.

      Thanks! Unfortunately, the error message I am getting is 204 No content which I am guessing means that it didn't return a token.

      Charlotte

        mcclell

        Okay so I actually saw this issue on a call today and invalid_client means you don't have something configured properly like in the case today they didn't have the correct Client ID.

        Cheers.

          6 days later

          I had this issue, only to find out you need to use the value of your client secret instead of the Secret ID.

          That's what I was doing using the secret id instead of the value. Thanks!

          2 years later

          Dealing with OAuth2 errors can be a real headache, right? I feel your pain! It seems like the issue you're facing with Microsoft OAuth2 invalid client errors could stem from a few things, like mismatched credentials or configuration glitches. Double-checking your client ID and secret usually helps, but hey, it's tech—sometimes it's just a mysterious digital gremlin.

          Has anyone else tried tweaking their settings or reached out to Microsoft support? I've found their documentation can be a lifesaver, though it can feel like diving into the deep end of Digital Chill Mart.

          Write a Reply...