OpenID2 to OpenID Connect Migration

The basic techniques of using Yahoo OpenID Connect are described in

To migrate your current OpenID2.0 client to OpenID connect, the following steps should be performed:

If you don’t have a client created before for your OpenID2 app, you should create one first. Check this for more details -

When constructing the authorization request to /request_auth API,

  • Add scopes to the scope parameter of your request by mapping the value openid.ext1.required to standard OpenID Connect scope


    OpenID Connect scope



    Other scopes like first, last, country etc.


The user information requested will be encoded in the id token you get from /get_token API. (Details about the content of an id token

  • Add openid2 to the scope parameter, delimited by a space with other scope you actually need.

  • Add the openid2_realm parameter, use the same value as you put in openid.realm parameter when calling the OpenID 2 API.

  • Use the value of openid.return_to as the redirect_uri.

For example, if you are sending an OpenID 2 authorize request URL like

Now you should construct your OpenID Connect authorize request URL as{your_client_id}&response_type=code&

When getting back the ID Token, you need to decode it and verify the openid2_id by making a GET call to the obtained verified claimed ID with an Accept header set to application/json. This API will return a JSON with iss as its top level member. The value of the iss field must exactly match the iss in the ID Token.

For example, you get an id token with OpenID 2 Identifier like this:

{ “iss”: “”, …, “openid2_id”:”–” }

You should make a GET request to

GET /a/Xsg0e4k2zPyKEiPoBRIjNKfHdcG.gA– HTTP/1.1


Accept: application/json

HTTP /1.1 200 OK

Content-Type: application/json


“iss”: “


You should verify the iss field in the response matches the iss in id token.