- Getting started
- Data security and compliance
- Organizations
- Authentication and security
- Licensing
- Tenants and services
- Accounts and roles
- AI Trust Layer
- External applications
- Managing external OAuth applications
- Configuring fine-grained access for confidential apps
- App registrations
- Personal Access Tokens
- Notifications
- Logging
- Troubleshooting
- Migrating to Automation Cloud™
Managing external OAuth applications
As an admin, using the OAuth framework, you can delegate authorization to external applications. Once registered, these applications can make API calls to UiPath applications or resources scoped to the APIs you designate.
To register an external application so that it can use OAuth to access your UiPath resources:
Scopes are the permissions of the external application in relation to your UiPath resources.
If you don't know the application secret that was generated for an external application, you cannot recover it. But you can generate a new one.
To generate a new app secret:
After you register an external application, a developer must also set up the external application so that it properly authenticates, requests authorization from UiPath Identity Server, and then access the allowed UiPath resources.
To be able to perform those tasks, you must share the following information with them:
- the Application Type and Application ID, both of which are visible on the Admin > External Applications page
- the scopes added for each scope type. For some resources, the same name is used under both user and application scopes, so the type is also important.
-
if this is a confidential application, the application secret generated when you registered the external application.
Note: If you don't have the secret anymore, generate a new one as described above.
For more details on how to authenticate and authorize external apps as a developer, see External Apps in the API guide.