We use both Jira Cloud and Jira Server with GitHub. I have already installed the "new" GitHub integration for the Cloud (a while ago), but both the Server and Cloud were previously set up with the "old" DVCS integration.
I recently received two emails from GitHub that the old integrations (both Server and Cloud) have been using access tokens in a deprecated way.
On June 10th, 2020 at 11:55 (UTC) your application (Jira) used an access token (with the User-Agent Apache-HttpClient/4.5.12 (Java/1.8.0_252)) as part of a query parameter to access an endpoint through the GitHub API.
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 on a monthly basis.
Visit https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param for more information about suggested workarounds and removal dates.
The GitHub Team
The above "Jira" identifies the OAuth app in our GitHub for the old DVCS integration in Jira Cloud.
your application (JIRA Service Desk) used an access token (with the User-Agent Java/1.8.0_202)
From the second email, "JIRA Service Desk" identifies the OAuth app in our GitHub for the old DVCS integration in Jira Server.
So: What can I do about this?
Jira Server version as at that point a few days ago was 8.4.1, since upgraded to 8.5.5 (as part of Service Desk).
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events