If Yahoo is specified as the the external identity provider, a subset of Yahoo provider attributes can be used as the mapping attribute placeholder value.

The placeholder value must use the following syntax:

${providerAttributes.<Yahoo attribute name>}

When you create a new Yahoo identity provider entity, the POST request automatically maps the PingOne username attribute to the Yahoo sub attribute. The username attribute is the core mapping attribute; the default Yahoo attribute value is sub. It is also recommended that you map the PingOne email attribute to the Yahoo email attribute.

The request body for the email-to-email mapping looks like this, with the value attribute showing the Twitter email attribute expressed using the placeholder syntax:

{
    "name": "email",
    "update": "EMPTY_ONLY",
    "value": "${providerAttributes.email}"
}

The POST /environments/{environmentId}/identityProviders operation adds a new identity provider resource to the specified environment.

When the type property value is set to YAHOO, Yahoo’s clientId and clientSecret property values are required in the request body.

Yahoo identity provider settings data model

Property Description
clientId A string that specifies the application ID from Yahoo. This is a required property.
clientSecret A string that specifies the application secret from Yahoo. This is a required property.

Yahoo core attributes

Property Description
sub A string that specifies the core Yahoo attribute. The default value is ${providerAttributes.sub} and the default update value is EMPTY_ONLY.

Yahoo provider attributes

Permission Provider attributes
openid sub
email email
profile Options are: name, given_name, family_name, picture, nickname, locale