The following tables describe the HTTP request methods you can use with the
/pingone/connections
and /riskPolicies
endpoints.
/pingone/connections
endpoint
HTTP Request Method | Description |
---|---|
|
Retrieves a list of all your current PingOne connections. |
|
Creates a new PingOne connection. To create a new connection, follow the PingOneConnectionView operation model in the PingAccess admin API docs. Note:
Whenever you create or edit a PingOne connection in PingAccess, PingAccess validates the credential specified within the connection to make sure it can reach any required runtime metadata, such as a risk API endpoint. After you've created a connection, you can assign it to a
specific risk policy through the |
|
Retrieves ( |
/riskPolicies
endpoint
HTTP Request Method | Description |
---|---|
|
Retrieves a list of all your current risk policies. |
|
Creates a new risk policy. To create a new risk policy, follow
the RiskPolicyView operational model in
the PingAccess API docs.
For more information on how to fill out the
configuration and
After you've created a risk policy, you can assign it to a
specific application or application resource through the
Note:
PingOne risk policies depend on mapping user identity attributes to the risk evaluation requests, so the PingAccess admin API will prevent you from saving an unprotected application or resource with a risk policy reference. |
|
Retrieves ( |
|
Retrieves a list of descriptors for all the different types of risk policies that PingAccess accepts as input. The descriptors explain what information is needed to fill out each type of risk policy. Note:
Currently, PingAccess only accepts the PingOne risk policy type. For a more detailed summary of how to fill out a PingOne risk policy, see Creating a PingAccess risk policy. |
|
Retrieves the descriptors for a single type of risk policy, such as a PingOne risk policy. For more information on the types of risk policies that PingAccess accepts as input, see
the previous table entry,
|