• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Buried in cloud files? We can help with Spring cleaning!

    Whether you use Dropbox, Drive, G-Suite, OneDrive, Gmail, Slack, Notion, or all of the above, Dokkio will organize your files for you. Try Dokkio (from the makers of PBworks) for free today.

  • Dokkio (from the makers of PBworks) was #2 on Product Hunt! Check out what people are saying by clicking here.

View
 

OpenID Language Preference

Page history last edited by Allen Tom 13 years, 3 months ago

Proposal for an OpenID Language Preference Extension

Relying Parties should be able to pass the user's language preference to the OpenID Provider to help the OP display its OpenID screens in the user's preferred language.

OpenID Providers that serve an international audience may have a single OpenID Provider Identifier for all its users, regardless of the user's language preference. For instance, all example.com users may be accustomed to initiating the sign in process by entering http://openid.example.com on an RP. Because the OP Identifier is language neutral, the OP cannot determine which language to display its Login screen if the user is not already signed in, possibly leading to a confusing sign in flow after being redirected from the RP.

Language Preference Parameter

RPs can specify the preferred language by passing an optional parameter called xopenid_lang_pref using the same format as defined in the OAuth Language Preference extension.

If the OP does not support the preferred language, the OP should display its OpenID sign in screens using the OP's default language.

Examples

Yahoo has an experimental implementation of this proposal.

Comments (1)

Breno de Medeiros said

at 7:00 pm on Jan 5, 2009

The examples are not conforming with http://www.rfc-editor.org/rfc/bcp/bcp47.txt, which is the closest to a recognized best-practice in how to encode language preferences.

The example has for Taiwanese: value=tw; I think it should say zh-TW. For an instance of when the above proposal would not work, consider Switzerland (CH). If you send xopenid_lang_pref=CH, should this be resolved to fr-CH, or de-CH?

You don't have permission to comment on this page.