Skip to main content

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

Customizing how UiPath Orchestrator authenticates calls from Pega Platform

Updated on April 6, 2022

Optionally, you can adjust to your security best practices by changing the default method that UiPath Orchestrator uses for authenticating service calls from your Pega Platform application.

Pega Platform uses service calls to establish communication between your application and UiPath Orchestrator. To complete a call, your application must obtain a valid authentication token. The out-of-the-box configuration uses the pyGetUIPathAuthToken REST service to fetch the token by providing the client secret parameter. If your implementation requires fetching the token through a different mechanism, you can customize the D_pyGetUiPathAuthToken data page.
  1. In Dev Studio, select RecordsData ModelData Page.
  2. From the data page list, select the D_pyGetUiPathAuthToken data page.
  3. Specialize the data page rule in the current application layer by performing the following actions:
    1. In the top-right corner of the rule form, click Save as.
    2. On the Record Configuration screen configure the following parameters:
      Record labelApplication contextApply-to classRuleset version
    3. Click Create and open.
  4. Adjust the data page configuration to your business needs.
    For example: To use client credentials instead of the refresh token for on-premises authentication, you can adjust the Data Sources configuration to use a service equivalent to the default pyGetUIPathAuthToken REST service.
    For more information, see Data pages overview.
  5. Confirm your configuration by clicking Save.

    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. is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us