-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm getting a 401 error when I try to authenticate the integration #5
Comments
Hi sorry I was on holiday with no access to email. |
@TomCasavant - I was running into this too. I was trying out a different integration, and in the logs for that one, it stated: "Unable to fetch auth token. Error: (invalid_client) AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID" So I went and made sure I was using the correct secret value and that integration worked. So I then came back to this one, and made sure to use the correct value (I wasn't previously), and now it's connecting just fine. |
401 is generic when you get the Client ID/ Secret wrong (and probably other stuff..) For me, when creating the secret within Certificates & Secrets > |
this is exactly was my issue, taking secret ID instead of KEY , now it is working
this is exactly was my issue, taking secret ID instead of KEY , now it is working |
This may just be an issue w/ a security policy setup on my work account, but I'm getting this error
The text was updated successfully, but these errors were encountered: