# GitHub logins using deprecated authentication API?

**URL:** <https://meta.discourse.org/t/github-logins-using-deprecated-authentication-api/140566>\
**Category:** Support\
**Created:** [February 4, 2020, 10:27am UTC](https://meta.discourse.org/t/github-logins-using-deprecated-authentication-api/140566 "2020-02-04T10:27:36Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Curtis\_Rueden](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/curtis_rueden/32/84277_2.png) [@Curtis\_Rueden](https://meta.discourse.org/u/Curtis_Rueden)\
**Post date:** [February 4, 2020, 10:27am UTC](https://meta.discourse.org/t/github-logins-using-deprecated-authentication-api/140566/1 "2020-02-04T10:27:36Z")

</div>

I just received the following email from GitHub:

> Hi @ctrueden,
> 
> On February 4th, 2020 at 06:50 (UTC) your application ([forum.image.sc](http://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](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](https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api/#authenticating-using-query-parameters) 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?

---

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [February 4, 2020, 10:40am UTC](https://meta.discourse.org/t/github-logins-using-deprecated-authentication-api/140566/2 "2020-02-04T10:40:22Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![kkowalczyk](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kkowalczyk/32/105438_2.png) [@kkowalczyk](https://meta.discourse.org/u/kkowalczyk)\
**Post date:** [February 4, 2020, 11:17pm UTC](https://meta.discourse.org/t/github-logins-using-deprecated-authentication-api/140566/4 "2020-02-04T23:17:38Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [February 5, 2020, 8:08am UTC](https://meta.discourse.org/t/github-logins-using-deprecated-authentication-api/140566/5 "2020-02-05T08:08:47Z")

</div>

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

> <https://github.com/omniauth/omniauth-github/pull/84>
>
> Fixes #83 - authenticating using query parameters is deprecated:
> 
> https://deve…loper.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api/#authenticating-using-query-parameters

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

Edit: And now, waiting for

[https://github.com/omniauth/omniauth-github/issues/87](https://github.com/omniauth/omniauth-github/issues/87)

---

<div class="post-metadata">

**Author:** ![mcdanlj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mcdanlj/32/131829_2.png) [@mcdanlj](https://meta.discourse.org/u/mcdanlj)\
**Post date:** [February 6, 2020, 1:34pm UTC](https://meta.discourse.org/t/github-logins-using-deprecated-authentication-api/140566/6 "2020-02-06T13:34:22Z")

</div>

Thanks! ~~I see it’s merged upstream~~ waiting for the next step. Should we expect an out-of-cadence beta release of Disc_ourse_¹ 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…

---

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [February 6, 2020, 1:37pm UTC](https://meta.discourse.org/t/github-logins-using-deprecated-authentication-api/140566/7 "2020-02-06T13:37:24Z")

</div>

> [@mcdanlj](#):
>
> Discord

:discourse:

> [@mcdanlj](#):
>
> Should we expect an out-of-cadence beta release

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.

---

<div class="post-metadata">

**Author:** ![dnsmichi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dnsmichi/32/379505_2.png) [@dnsmichi](https://meta.discourse.org/u/dnsmichi)\
**Post date:** [February 10, 2020, 8:47am UTC](https://meta.discourse.org/t/github-logins-using-deprecated-authentication-api/140566/8 "2020-02-10T08:47:07Z")

</div>

If the release does not happen soon enough, it may be applicable to pin that specific ref for omniauth-github in the Gemfile, suggested [here](https://github.com/omniauth/omniauth-github/issues/88#issuecomment-583232323).

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

```

There also was a README update [commit](https://github.com/omniauth/omniauth-github/commit/967d76979b6bf9bb0b71b255ad204f8931f65be6) which suggests to use git master.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [February 11, 2020, 4:20am UTC](https://meta.discourse.org/t/github-logins-using-deprecated-authentication-api/140566/9 "2020-02-11T04:20:02Z")

</div>

We are working on it and have specific plans for both eventualities.

---

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [February 11, 2020, 9:48am UTC](https://meta.discourse.org/t/github-logins-using-deprecated-authentication-api/140566/10 "2020-02-11T09:48:37Z")

</div>

This should now be resolved on tests-passed, beta and stable. We’ll be rolling out the change on our hosting in the next few days

[https://github.com/discourse/discourse/commit/3a906ff0e61c161ad6c7857d700f37721cbc6b45](https://github.com/discourse/discourse/commit/3a906ff0e61c161ad6c7857d700f37721cbc6b45)

---

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [February 12, 2020, 6:00pm UTC](https://meta.discourse.org/t/github-logins-using-deprecated-authentication-api/140566/11 "2020-02-12T18:00:00Z")

</div>

This topic was automatically closed after 32 hours. New replies are no longer allowed.
