Connexions GitHub utilisant l'API d'authentification obsolète ?

Soutien
1

I just received the following email from GitHub:

Hi @ctrueden,

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:

https://api.github.com/user

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 Deprecated APIs and authentication | GitHub Developer Guide for more information.

Thanks,
The GitHub Team

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?

13 « J'aime »
2

Thanks for sharing the email Curtis. I’ll take a look into this - it looks like we will need some updates on our end.

17 « J'aime »
4

Just a “me too” post. I got the same email from GitHub.

3 « J'aime »
5

FYI, we’re tracking this PR in the authentication library which Discourse uses. As soon as that’s merged, we can update:

(If it takes too long, we’ll implement ourselves)

Edit: And now, waiting for

17 « J'aime »
6

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…

1 « J'aime »
7

:discourse:

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.

13 « J'aime »
8

Si la version n’a pas lieu assez rapidement, il peut être pertinent de figer cette référence spécifique pour omniauth-github dans le fichier Gemfile, comme suggéré ici.

gem 'omniauth-github', git: 'https://github.com/omniauth/omniauth-github.git', ref: '967d769'

Il y a également eu une mise à jour du README dans ce commit qui recommande d’utiliser la branche master de Git.

9

Nous y travaillons et avons des plans précis pour les deux éventualités.

5 « J'aime »
10

Cela devrait désormais être résolu sur tests-passé, bêta et stable. Nous déploierons la modification sur notre hébergement dans les prochains jours.

11 « J'aime »
11

Ce sujet a été automatiquement fermé après 32 heures. De nouvelles réponses ne sont plus autorisées.