Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Deprecation notice for authentication via URL query parameters
See original GitHub issueGitHub is sending me a deprecation notice for authentication via URL query parameters, by GitHub’s Jira integration for Atlassian.
Please use the Authorization HTTP header instead as using the access_token query parameter is deprecated.
Depending on your API usage, we’ll be sending you this email reminder once every 3 days for each token and User-Agent used in API calls made on your behalf. Just one URL that was accessed with a token and User-Agent combination will be listed in the email reminder, not all.
Visit https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api/#authenticating-using-query-parameters for more information.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:29
- Comments:24 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@DMonCode We get this error with the “new” GitHub Jira integration, not with the DVCS connector.
I’ll try to give a little backstory (given my limited knowledge on this) to help you arrive at the desired state:
When Atlassian first wrote a GitHub to Jira connector, it was something that users manually created and installed. You made your own OAuth App and pointed the webhooks and setup at your custom Jira URL. This app allowed Jira to configure GitHub Repo webhooks to send data from GitHub to Jira.
The GitHub owned integration is wholly separate from the process above. It is an Application that must be installed into your Jira Organization and your GitHub organization, and uses Application Webhooks (instead of Repo webhooks). These webhooks are delivered to the GitHub+Jira Service (which we manage, code is in this repo) to update your Jira instance based on the Jira devinfo API.
Unless you are using the “Developer Settings -> OAuth Apps” version (the old way to do jira integration), delete that app that your organization owns and manages from the Advanced Tab. This is not part of the Jira+GitHub sync tool that GitHub manages and we don’t control it. Our App should be listed under your “Installed Apps” section only.
Let me know if that clears some things up, thanks.