-
Notifications
You must be signed in to change notification settings - Fork 19
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
Getting 400 error after upgrading to latest TC and plugin. #52
Comments
https://youtrack.jetbrains.com/issue/TW-66625 Doesnt this work for you? |
Please try 0.7.0 version of the plugin |
Hello, Also facing similar issue with error 400. Yesterday I've updated plugin to version 0.7.0. TC server in version 2020.1.3. Same behavior like for previous version of plugin. Also I've just tried solution from @SithVicious but unfortunately without any luck. Are there any possible ways to debug this issue deeper? |
Definitely rebooted after?
…-Paul
On 16 Sep 2020, at 5:03 pm, pstabno <[email protected]> wrote:
Hello,
Also facing similar issue with error 400. Yesterday I've updated plugin to version 0.7.0. TC server in version 2020.1.3. Same behavior like for previous version of plugin. Also I've just tried solution from @SithVicious<https://github.com/SithVicious> but unfortunately without any luck. Are there any possible ways to debug this issue deeper?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#52 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGCHFHSVPKQY7DPPJTJMFOTSGBPNJANCNFSM4QBWIF2A>.
|
Yes - even whole VM that is hosting this instance. |
Even tried AzureAD with proxy - still no success. We are getting out of ideas :/ |
Also I would like to ask - should we go only with default attributes and claims? or there should be any custom ones added? Also - just for my curiosity - why plugin is using ApplicationID instead of certificate directly? |
Hi all
We started getting the following error after upgrading quite a few of the components. We also created the Azure AD enterprise app again but no luck
"400 Marked request as unauthenticated since failed to parse JWT from retrieved id_token" (token follows)
I suspect it has to do with a certificate mismatch in TC and the AAD plugin. Anyone able to help?
The text was updated successfully, but these errors were encountered: