Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Authenticating Pega Infinity Server user access

Updated on May 27, 2022

To publish, list, or delete a Cosmos digital experience (DX) component, you require authentication to access the resources on the Pega Infinity Server.

Note: After completing the authentication, you have to reauthenticate yourself after the default timeout of 15 minutes. You can change the timeout period by editing the REST API Auth 2.0 Client registration record. The record contains a clientID that matches the configuration that is contained in the tasks.config.json file of each component.
Note: Custom DX components require you to use the OAuth 2.0 authentication protocol.
  1. Log in to the Pega Infinity Server.
  2. In Dev Studio, click RecordsSecurityOAuth 2.0 Client Registration, and then open the DX-CustomComponents record.
  3. Click Regenerate Client Secret.
  4. Copy the Client Credentials (the Client ID, Client Secret, and Access token endpoint), and then save the record.
  5. Update the task.config.json file by using the copied values:
        "server-config": {   
            "server": "https://127.0.0.1:8080/prweb",   
            "user": "customcomponentoperator",   
            "password": "pwd",   
            "clientId": "<mention client ID here>",   
            "clientSecret": "<mention client secret here>",  
            "accessTokenUri": "https://127.0.0.1:8080/prweb/PRRestService/oauth2/v1/token"
        }
  6. Run the following command to initiate authentication:
    npm run authenticate
Result: You now have authentication to publish, list, or delete Cosmos DX components.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us