This week we will be removing support for Yahoo logins from Discourse.
Why?
It gets very little use. Across sites we manage, less than 0.3% of social login attempts are performed using Yahoo
It is the last provider using the OpenID2.0 specification, which has been declared obsolete 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.
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 and OpenID Connect plugins should be flexible enough for most requirements.
Con la prossima release alle porte, il supporto legacy per OpenID 2.0 è stato rimosso dal core di Discourse. Non era utilizzato né dal core né da alcun plugin ufficiale, e l’avviso di deprecazione è presente da aprile 2019.
Nel caso in cui qualcuno non avesse visto l’avviso di deprecazione, la tabella del database contenente le associazioni degli account non è ancora stata eliminata. Qualsiasi tentativo di accedervi tramite ActiveRecord genererà un’eccezione. Sarà eliminata prima della versione 2.5.