- Release Notes
- Getting Started
- Governance
- Logging
Settings for Integration Service policies
This page describes how to manage connectors and authentication options using Integration Service policies.
The policy configuration screen lists all the connectors available in the Integration Service catalog. Use the checkboxes to enable or disable any connector.
By default, all the connectors are enabled, and all official settings and authentication options are enabled for each connector.
Select the More options button menu and select Configure connector to view a connector's supported authentication types.
The Bring your own app option is enabled by default for all connectors using the OAuth 2.0 authorization code authentication method. This means you are expected to create and configure your own private OAuth 2.0 application.
You can enable or disable authentication types for users inside your organization. Once you deploy the policy, the connector's connection creation screen will only include the authentication types you enabled.
For each authentication type, select the More button menu to configure authentication parameters.
You can pre-define values for any of the authentication parameters available for a given connector. For example, you can:
- Hardcode the OpenAI API Key for anyone building workflows on a given tenant.
- Configure the Bring your own app option for Microsoft Outlook 365 by setting the application's Client ID, Client Secret, and Scope.
- Configure a custom Site URL for Jira.
Follow the steps described in Deploy Governance Policies to deploy the policy.
Integration Service policies are cached. It can take up to five minutes for changes to existing policies to be reflected in the connector catalog.
When a connector is disabled through Automation Ops, you can see the policy's effects throughout the rest of the UiPath Platform, as follows:
- In the Integration Service Connectors catalog, disabled connectors are listed separately. You cannot access the connector page or create a connection.
- In Studio, at design time, when you add an activity for a disabled connector, you receive the following error message: "The connector was disabled by an Automation Ops policy. Check with your administrator or review the policy."
- In Orchestrator, Apps, or other UiPath products that use Integration Service connections, you receive the same error message when trying to create a connection for a disabled connector.
- Policies can overwrite the Integration Service official catalog configuration.
- New policies do not affect existing connections and running workflows. Policy restrictions impact only new connections.
- Connection management (like updating a connection) is no longer possible for a connector governed through an Automation Ops policy. An attempt to do so prompts a notification to contact your administrator.
-
Custom connector management through Automation Ops is not possible at the moment.
- Administrators can always overwrite policies using UiPath Automation Ops.
