# Removing Yahoo login from Core, and deprecating OpenID 2.0

**URL:** https://meta.discourse.org/t/removing-yahoo-login-from-core-and-deprecating-openid-2-0/113249
**Category:** Announcements
**Created:** [4월 2, 2019, 5:17오후 UTC](https://meta.discourse.org/t/removing-yahoo-login-from-core-and-deprecating-openid-2-0/113249 "2019-04-02T17:17:32Z")
**Posts on this page:** 3
**Page:** 1

<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: [4월 2, 2019, 5:17오후 UTC](https://meta.discourse.org/t/removing-yahoo-login-from-core-and-deprecating-openid-2-0/113249/1 "2019-04-02T17:17:32Z")

</div>

This week we will be removing support for Yahoo logins from Discourse.

[https://github.com/discourse/discourse/pull/7310](https://github.com/discourse/discourse/pull/7310)

## Why?

1. It gets **very** little use. Across sites we manage, less than 0.3% of social login attempts are performed using Yahoo

2. It is the last provider using the OpenID2.0 specification, which has been [declared obsolete](https://openid.net/developers/specs/) by the OpenID foundation. It does not have the same security features as OAuth2 / OpenID Connect.

## What about users that have already registered using Yahoo?

They can log in with email, log in with another social provider (with a matching email), or use the ‘Reset Password’ button.

## But I still want Yahoo login on my forum!

No problem! You can use Yahoo’s OpenID Connect implementation with our OpenID Connect plugin. I’ve added some Yahoo specific instructions to [the OpenID Connect setup instructions](https://meta.discourse.org/t/openid-connect-authentication-plugin/103632).

## I use OpenID 2.0 in one of my plugins

For now they will continue to work, but will log a deprecation notice. Support will be removed in the next major release. You should look into migrating to a more modern authentication protocol. Our [basic OAuth2](https://meta.discourse.org/t/oauth2-basic-support/33879) and [OpenID Connect](https://meta.discourse.org/t/openid-connect-authentication-plugin/103632) plugins should be flexible enough for most requirements.

---

<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: [2월 7, 2020, 6:11오후 UTC](https://meta.discourse.org/t/removing-yahoo-login-from-core-and-deprecating-openid-2-0/113249/2 "2020-02-07T18:11:09Z")

</div>

> [@david](#):
>
> 다음 주요 릴리스에서 지원이 제거됩니다

다음 릴리스가 코앞에 다가온 가운데, 레거시 OpenID 2.0 지원이 Discourse 코어에서 제거되었습니다. 이는 코어나 공식 플러그인 어디에서도 사용되지 않고 있었으며, 비추천(deprecation) 공지사항은 2019년 4월부터 존재해 왔습니다.

> <https://github.com/discourse/discourse/commit/5919618a87675cfcba9a62621c8b0eb07587ee96>
>
> This is not used in core or official plugins, and has been printing a deprecatio…n notice since v2.3.0beta4. All OpenID 2.0 code and dependencies have been dropped. The user\_open\_ids table remains for now, in case anyone has missed the deprecation notice, and needs to migrate their data.
> 
> Context at https://meta.discourse.org/t/-/113249

혹시 비추천 공지사항을 아직 보지 못한 분들을 위해 안내드립니다. 계정 연관성(account associations)을 포함하는 데이터베이스 테이블은 아직 삭제되지 않았습니다. ActiveRecord를 통해 이를 접근하려는 시도는 예외를 발생시킵니다. 해당 테이블은 v2.5 이전까지 삭제될 예정입니다.

---

<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: [12월 20, 2020, 11:16오후 UTC](https://meta.discourse.org/t/removing-yahoo-login-from-core-and-deprecating-openid-2-0/113249/3 "2020-12-20T23:16:51Z")

</div>


