[FOLIO-2461] Update GitHub API auth in Jira, brownout March 17, 2021 Created: 10/Feb/20  Updated: 27/Apr/21  Resolved: 27/Apr/21

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P2
Reporter: Peter Murray Assignee: John Malconian
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: DevOps: Sprint 105, DevOps Sprint 109, DevOps Sprint 107, DevOps Sprint 108, DevOps Sprint 111, DevOps Sprint 112, DevOps Sprint 106, DevOps Sprint 113
Development Team: FOLIO DevOps

 Description   

On January 6th, 2021 at 12:59 (UTC) your application (FOLIO Jira) used an access token (with the User-Agent Java/1.8.0_74) as part of a query parameter to access an endpoint through the GitHub API.

https://api.github.com/repositories/327300290/hooks

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.

Deprecation timeline
Brownouts

During a brownout, authentication using query parameters will temporarily fail. The goal is to trigger alerts (assuming there are any) on our customers' services to help them find unmigrated authentication calls.

The brownouts are scheduled for:

  • March 17, 2021
    • From 07:00 UTC to 10:00 UTC
    • From 16:00 UTC to 19:00 UTC
  • April 14, 2021
    • From 07:00 UTC to 10:00 UTC
    • From 16:00 UTC to 19:00 UTC

Removal date

All authentication using query parameters will return a status code of 401 like all other auth failures starting on:

  • May 5, 2021 at 16:00 UTC


 Comments   
Comment by Julian Ladisch [ 06/Jan/21 ]

Please adjust team and sprint as needed!

Comment by Peter Murray [ 27/Apr/21 ]

I don't think I've seen an email from GitHub about this after Jira was updated. Okay to close?

Generated at Thu Feb 08 23:20:48 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.