Oauth2.0

[Hardik_Durgam]

Hello all it would be really helpful if someone can explain me how to integrate Oauth2.0 with UiPath and its properties.

Regards,
Hardik Durgam.

[nikhil.girish]

Hi @Hardik_Durgam

kindly refer the below links
https://docs.uipath.com/orchestrator/reference/using-oauth-for-external-apps

How to Configure OAuth2 Connection to JIRA in Uipath Studio Pro

hope this helps

[Tuannna1 (Tuan Anh)]

@Hardik_Durgam

Hello all it would be really helpful if someone can explain me how to integrate Oauth2.0 with UiPath and its properties

OAuth 2.0 is a protocol used to secure authorization to access resources. To integrate OAuth 2.0 with UiPath, you need to perform the following steps:

1. Obtain OAuth 2.0 credentials: Depending on the OAuth 2.0 provider, you may need to register your application and obtain client ID, client secret, and a redirect URL.
2. Use the UiPath Web API activities to build a workflow that performs the OAuth 2.0 authorization flow. This usually involves sending a request to the authorization endpoint to get an authorization code, sending a request to the token endpoint to exchange the authorization code for an access token, and sending a request to the protected resource endpoint with the access token in the authorization header.
3. Store the access token securely: Depending on your use case, you may want to store the access token in a secure database or in an encrypted file.

Properties of OAuth 2.0 used in UiPath integration:

1. Grant Types: The grant types determine how the client application will receive an access token. UiPath supports several grant types such as authorization code, client credentials, password, and implicit.
2. Token endpoint: The token endpoint is the endpoint on the authorization server where the client application can exchange an authorization code for an access token.
3. Authorization endpoint: The authorization endpoint is the endpoint on the authorization server where the client application sends the user to authenticate and grant authorization.
4. Client ID and secret: The client ID and secret are used to identify the client application to the authorization server.
5. Access token: The access token is a string that grants access to the protected resource.
6. Redirect URL: The redirect URL is the URL that the authorization server will redirect the user to after they grant authorization.

[Hardik_Durgam]

@Tuannna1 thanks for such a detailed explanation.

Regards,
Hardik Durgam.