An OAuth client application interacts with an OAuth authorization server (AS) to obtain access tokens needed to call OAuth-protected services at the resource server (RS).
Use theto manage OAuth clients. This screen displays 20 clients at a time. You can sort the display order by name or ID. You can use the pagination controls to navigate through the rest of the clients or search clients by name or ID. A client is included in the search results so long as its name or ID is a partial, case-insensitive match to the search term.
- To add an client, click Add Client and complete the configuration on the Client screen.
- To edit a recently modified client, select it by its name and update its configuration on the Client screen.
- To enable or disable one or more clients, click their toggle switches and then click Save.
- To remove a client or cancel the removal request, use the Delete and Undelete workflow for the applicable client and then click Save.
PingFederate stores client records in XML files by default. On-disk storage allows you to manage clients using the administrative console and the administrative API. Client records are part of the configuration archive.
Alternatively, you can configure PingFederate to store client records externally, which provides the flexibility to manage client records via the OAuth Client Management Service or enable dynamic client registration for your partner-developers. In this scenario, client records are not part of the configuration archive. Instead, they are stored on a database server, a directory server, or some other storage medium through the use of the PingFederate SDK (see Defining an OAuth client datastore).