This process is two-fold:

  • Policy writers use the Policy Editor to publish policies in a deployment package to a deployment package store.
  • Updated deployment packages are picked up by the PingAuthorize Policy Decision Service from the deployment package store.
    Note:

    You configure the interval that the server checks for updates in the store during setup.

This allows a policy writer to deploy new policies without the manual process of exporting a deployment package that is then uploaded into the server through the administrative console.

The Deployment Manager can use deployment package stores that are based on:

  • A directory in the filesystem
  • An Amazon Simple Storage Service (Amazon S3) bucket
  • Azure Blob storage

Package stores hold deployment packages in a central location that the Policy Editor publishes to and the PingAuthorize server reads from.

To use the Deployment Manager:

  1. Define a deployment package store.
    Note:
    • For a filesystem store, you must have a directory on the filesystem that the Policy Editor has read-write access to.
    • Amazon S3 buckets must be configured with a secret key and an access key for use.
    • For Azure storage, you must set up an Azure storage account and a container. For later use, record the Connection string value found in your account's Access key settings.
  2. Use an options file to configure the Policy Editor to publish policies to a store.
  3. Create and deploy deployment packages to the deployment package store.
  4. Add the deployment package store for read access to the PingAuthorize Server:
    1. Add a filesystem deployment package store.
    2. Add an Amazon S3 deployment package store.
    3. Add an Azure deployment package store,
  5. Configure the Policy Decision Service to read from your deployment package store.