Configuring Postman
If you plan to use Postman to configure your connections, you’ll need to ensure that several collection variables are set and that Postman is correctly configured. You’ll also need to download the collection. Learn more in Download the Postman collection.
Steps
-
Add the API domain for your PingOne region to the collection variable apiPath, and then add the auth domain for the region to the collection variable authPath. Learn more in API requests in the PingOne Developers documentation.
-
Get an access token from a worker application. You can use an existing worker application or create a new one.
Either way, ensure that the Environment Admin and Client Application Developer roles are assigned. Learn more in Create an admin Worker app connection in the PingOne Developers documentation.
Then, get the token. Learn more in Get a PingOne admin access token in the PingOne Developers documentation.
To get a token from a different worker application in a different sandbox environment, run the token request endpoint using the client ID and client secret of the worker application to authenticate the request. Learn more in Worker applications in the PingOne Developers documentation.
Add the access token to the collection variable accessToken.
-
Choose the PingOne environment that will act as the OIDC identity provider, which will connect to the PingOne Advanced Services environment.
-
Add the environment ID to the collection variable envID.
-
Request the region domain and environment ID for your primary region from PingOne Advanced Services.
-
Add the auth domain for the PingOne Advanced Services environment to the collection variable p1asAuthPath.
-
Add the environment ID for the PingOne Advanced Services tenant to the collection variable p1asEnvID.