A discussion about GitHub deprecating authentication via query parameters in their API, prompted by an email received by user Curtis_Rueden. The email warns that using access tokens in URLs (e.g., https://api.github.com/user?access_token=...) is deprecated and should be replaced with the Authorization header. Users David, kkowalczyk, and others confirm receiving similar notifications. David explains that Discourse relies on the omniauth-github library, which needs an update to comply with the new authentication method. A PR has been submitted and is under review, with plans to backport the fix to beta and stable branches to prevent ongoing deprecation warnings. Users are advised to monitor the topic for updates. David confirms the fix is now live on tests-passed, beta, and stable, with a rollout on hosted Discourse expected soon.
On February 4th, 2020 at 06:50 (UTC) your application (forum.image.sc) used an access token (with the User-Agent Faraday v1.0.0) 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 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.
Is this something that needs to be changed in my forum’s configuration? Or is an update to the Discourse code needed? Or is something else going on here?
Thanks! I see it’s merged upstream waiting for the next step. Should we expect an out-of-cadence beta release of Discourse¹ for this, or just watch for an update that addresses this and do an out-of-cadence site update?
¹ Argh, I was just having a conversation on a Discourse forum about Discord with someone, and crossed neurons as a result…
We’ll be updating tests-passed as normal. Given it should be a simple change, we can also backport it to beta/stable so that people can avoid the constant deprecation emails. Keep an eye on this topic to know when the update is available.