Adding a custom resource
Use the Resources page to add a custom resource to PingOne.
Steps
-
Go to Applications → Resources.
-
Click the + icon.
-
For Create resource profile, enter the following information:
-
Resource name. A unique identifier for the resource.
-
Audience. (Optional) The intended audience for the resource. If you don’t provide a value, PingOne will default to the resource name.
-
Description. (Optional) A brief characterization of the resource.
-
Access token time to live. The maximum time that the access token will be valid for use in the application, in seconds.
-
-
Click Next.
-
For Attributes, map resource attributes to user attributes in PingOne.
-
Enter a resource attribute and then select the corresponding PingOne attribute from the list.
For example, you could map the
OIDC family_name
attribute to the PingOneFamily Name
attribute. You can add more attributes after you have created the custom resource. Learn more in Mapping attributes. -
Enter a resource attribute and then select the corresponding PingOne attribute from the list.
Enter an OIDC attribute and the desired PingOne mapping. Click the Gears icon to use advanced expressions. Learn more in Using the expression builder.
-
To delete an attribute, click the Trash icon for the appropriate attribute.
Resources can use JSON attributes in their attribute mappings. You can use these attributes to pass complex information to applications through an access token. Learn more in Adding user attributes.
-
-
Click Next.
-
For Scopes, configure the appropriate scopes for the resource. Each resource can have one or more scopes. To add a scope, click Add scope. Enter the following:
-
Scope name: The name of the scope to be used for this resource. Scopes are defined by the resource server.
-
Description (optional): A brief characterization of the scope.
-
-
Click Save.
Next steps
You can add more scopes to the custom resource. Learn more in Editing a resource.
With PingOne Authorize, you can define application resources and permissions to set up role-based access control for the custom resource. Learn more in Application permissions and Editing a resource.