Unable to authenticate to Jira Server/DC from the Atlassian VS Code Extension
Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.
When attempting to connect to your Jira Data Center instance via the "Add Custom Jira Site" feature of Atlassian Jira and Bitbucket (Official) VS Code extension, the login fails with an error message:
Error authenticating with Jira: Error: <ERROR MESSAGE>
You are otherwise able to authenticate to and use Jira normally when not using the extension.
Jira Server or Data Center
- You are using the Jira and Bitbucket (Official) VS Code extension
There are a number of potential causes
- The SSL certificate required to connect is not publically trusted or has an imcomplete chain. Known error messages include:
Error authenticating with Jira: Error: unable to verify the first certificate
- Unable to connect to the Jira Server as a proxy server is required, or must be bypassed. Known error messages include:
Error authenticating with Jira: Request failed with status code 400
- Your Jira requires a third party SSO authenticator to log in
- When authenticating, enable the Use Custom SSL Settings toggle
- Check on of the custom SSL options, and specify the full path to the certificate bundle or certificate file
Edit your vscode settings.json
Add or edit your proxy settings accordingly. For example:
To specify no proxy, use
To exclude a specific domain from proxy lookup, add a comma delimited list of domains into your operating system environment variable
The VSCode extension does not currently support third party SSO.
For more information please see Atlascode Issue #237