Managing templates

PingCentral

bundle
pingcentral-19
ft:publication_title
PingCentral
Product_Version_ce
PingCentral 1.9
category
Administrator
Audience
Developer
Product
pc-19
pingcentral
ContentType_ce
Page created: 8 Oct 2021 |
Page updated: 21 Apr 2022
| 1 min read

1.9 Product PingCentral Developer Audience Administrator OAuth Standards, specifications, and protocols OpenID Connect SAML

When you create a PingCentral template based on an existing PingFederate or PingAccess application, or add an existing PingFederate or PingCentral application to PingCentral, the raw JSON is saved to PingCentral.

PingCentral does not display the entire JSON file when you select an application, but the most relevant information is provided to help you distinguish between applications.

Creating OAuth and OIDC application templates

Page created: 8 Oct 2021 |
Page updated: 21 Apr 2022
| 1 min read

1.9 Product PingCentral Developer Audience Administrator OAuth Standards, specifications, and protocols OpenID Connect SAML

For OAuth or OIDC application templates, the following items are saved:
  • The client application.
  • The ATM, if one exists.
  • The parent ATM, if one exists.
  • The OIDC policy, if one exists.
  • Definitions of exclusive scopes referenced by the client.

Refer to OIDC connection orchestration to see a diagram of the PingFederate items orchestrated by PingCentral.

To create a template, select a client configuration that exists in a PingFederate environment to replicate. PingCentral retrieves this configuration from PingFederate and saves it as a building block for future applications.

  1. Select Templates to see a list of available templates.
  2. Click Add Template, select either an OAuth or OpenID Connect template from the Integration Type page and click Next.
  3. On the Select OAuth Client or OIDC Client page, select the PingFederate environment that hosts the client application you want to use as a template, and then select the application itself from the Client list.
    Details regarding the selected client display.

    This example shows the information that displays when an OAuth client is selected.
  4. To see the JSON for the application, click Review Configuration.
  5. On the Name Template page, add a name and description for your template. This information will help application owners select the appropriate template.
  6. Select an icon to represent your template. The icon you choose will display with the template name and description.
  7. Click Save and Close.
    You will see the new template in the list of available application templates. Application owners will see the new template on the Select Template page.

    This example shows the Select Template screen, which lists the templates available for application owners to use.

Creating SAML SP application templates

Page created: 8 Oct 2021 |
Page updated: 21 Apr 2022
| 1 min read

1.9 Product PingCentral Developer Audience Administrator OAuth Standards, specifications, and protocols OpenID Connect SAML

For SAML SP connection templates, the following items are saved:
  • Connection information.
  • Attribute names defined in the associated authentication policy contract.

Refer to SAML connection orchestration to see a diagram of the PingFederate items orchestrated by PingCentral.

To create a template, select a connection configuration that exists in a PingFederate environment to replicate. PingCentral retrieves this configuration from PingFederate and saves it as a building block for future applications.

  1. Select Templates to see a list of available templates.
  2. Click Add Template and select SAML from the Integration Type page. Click Next.
  3. On the Select SAML Connection page, select the PingFederate environment that hosts the connection you want to use as a template, and then select the connection from the Connection list.
    Details regarding the connection display.

    This example shows the information that displays when a SAML connection is selected.
  4. To see the JSON for the SAML connection, click Review Configuration.
  5. On the Name Template page, add a name and description for your template. This information will help application owners select the appropriate template.
  6. Select an icon to represent your template. The icon you choose will display with the template name and description.
  7. Click Save and Close.
    You will see the new template in the list of available application templates. Application owners will see the new template on the Select Template page.

    This example shows the Select Template screen, which lists the templates available for application owners to use.

Creating PingAccess application templates

Page created: 8 Oct 2021 |
Page updated: 21 Apr 2022
| 2 min read

1.9 Product PingCentral Developer Audience Administrator OAuth Standards, specifications, and protocols OpenID Connect SAML

For PingAccess applications, the following items are saved:
  • Virtual host information
  • The context root
  • Application type (Web, API, or Web + API)
  • Destination type (site or agent)
  • Web session information
  • Identity mappings
  • Resource definitions
  • The rules with the application and resource policies
Note:

Virtual resources are available in PingAccess version 6.2 or later, but are not yet supported in PingCentral.

To create a PingAccess template, select a configuration that exists in a PingAccess environment to replicate. PingCentral retrieves this configuration from PingAccess and saves it as a building block for future applications.

  1. To see a list of available templates, select Templates .
  2. Click Add Template.
  3. From the Integration Type page, select PingAccess. Click Next.
  4. On the Select PingAccess Application page, from the Environment list, select the PingAccess environment that hosts the application you want to use as a template, and then from the Application list, select the application.
    The application details display next to the Application list.

    This example shows the information that displays when a Web + API application is selected on the Select PingAccess Application page. A This information includes Description, Virtual Hosts, Context Root, Application Type, Destination Type, Site, Access Validation, Web Session, Client ID, API Identity Mapping, Web Identity Mapping, Resources, and Rules.
  5. To see the JSON for the PingAccess application, click Review Configuration.
  6. On the Name Template page, add a name and description for your template.

    This information helps application owners select the appropriate template.

  7. Select an icon to represent your template.

    The icon you choose displays with the template name and description.

  8. Click Save and Close.
    The new template appears in the list of available application templates. Application owners can see the new template on the Select Template page.

    A screen capture showing the Select Template page, which lists the templates available for application owners to use. The displayed available templates are Public Application, Internal Application (and Partners), Access Control Policy, Existing Application. Public Application is an OpenID Connect template. Internal Application (and Partners) is an OAuth template. Access Control Policy is a PingAccess template. The screen capture also shows a tip bar for how to choose the right template.