Important:

The Authorization Policy Decision APIs feature requires PingAuthorize Premier. For more information, contact your Ping Identity account representative.

The PingAuthorize Server's main functionality is to enforce fine-grained policies for data accessed through an APIapplication programming interface (API) A specification of interactions available for building software to access an application or service.. However, organizations might need to use the core Policy Decision Service for non-API use cases. For example, an application server might use it to request policy decisions when generating dynamic web content. In this configuration, PingAuthorize Server becomes the policy decision point (PDP), and the application server becomes the policy enforcement point (PEP).

The Authorization Policy Decision APIs consist of the following PDP APIs:

  • XACML-JSON PDP API

    This API provides a standards-based interface.

    Standards-based enforcement points request policy decisions based on a subset of the XACML-JSON standard. For more information, see XACML 3.0 JSON Profile 1.1.

  • JSONJSON (JavaScript Object Notation) An open, lightweight data-interchange format that uses human-readable text to store and transmit data. PDP API

    This API provides a simpler interface.

Note:

The Authorization Policy Decision APIs can indicate when a request or response triggers advice, but the application server must implement the advice.

To make a PDP API available, you must:
  • Configure the PingAuthorize Server with a feature-enabled license during setup.
  • Configure the Policy Decision Point Service. For more information, see Use policies in a production environment.
  • For the XACML-JSON PDP API, configure an access tokenaccess token A data object by which a client authenticates to a resource server and lays claim to authorizations for accessing particular resources. validator. For more information, see Access Token Validators.