How to re-initialize the Interactive Token

Help Activities
, ,
1

Scenario →

i) Dependency is UiPath.MicrosoftOffice365.Activities with v1.14.1

ii) Activity is Microsoft Office 365 Scope

iii) For the above activity i have set Authentication Type as Interactive Token, Enviornment as Global and OAuthApplication as UiPath

iv) While Debugging for the first time, it opens a pop up/ redirects to a page for connecting to your microsoft account. During this step after i had connected halfway, it had failed due to browser/network error.

v) But in UiPath it doesnt ask to connect again and throws error when using activites under the package specified. ( Error → Invalid hostname for this tenancy
Inner error)

vi) To resolve this error, I had thought to reset the Interactive Token and try again, but am unsure how to proceed with resetting the Token. It would be a great help if anyone could guide me on a way to re-initialize the Interactive Token.

2

Hello @Quenton_Wayne_Rebello

Try this Steps

  1. Clear Existing Tokens: Before re-initializing the Interactive Token, you should clear any existing tokens that may have been saved. Follow these steps:a. Open your Windows Credential Manager. b. Under “Generic Credentials,” look for any entries related to your Microsoft Office 365 connection or UiPath. Delete these entries. c. Additionally, clear your browser cache and cookies to ensure no cached authentication information is causing issues.
  2. Reinitialize the Interactive Token: To re-initialize the Interactive Token, you can follow these steps:a. Open your UiPath project. b. In the Microsoft Office 365 Scope activity properties, check if there is an option to “Reauthenticate” or “Clear Credentials.” If there is, select it, and then run your workflow again.
  3. Check Redirect URIs and Permissions: Ensure that you have configured the redirect URIs and permissions correctly in your Azure AD application registration for UiPath. If they are not set up correctly, it can lead to authentication issues.
  4. Retry Connection: If the above steps do not resolve the issue, you may need to retry the connection from scratch:a. Open the Microsoft Office 365 Scope activity. b. In the “Authentication Type” dropdown, select “Interactive Token” again. c. Click on the “Environment” dropdown and select “Global.” d. Set the “OAuthApplication” to “UiPath” as you mentioned.
  5. Run the Workflow: Try running the workflow again. This should trigger the authentication process and open a pop-up or redirect to the Microsoft login page for you to re-enter your credentials.
1 Like
3

@Quenton_Wayne_Rebello

Basically why you want to use interactive token instead use app id and seret that way ot would not ask for authentication

cheers

4

Since i am running it localy to build a small workflow, I have planned to run it on Interactive Token mode. Also I have limitized access to attain app id and secret from azure.

5

@Quenton_Wayne_Rebello

Generally here is where it stored he cached info of the tokens and all…try to delete it and then retry

C:\Users\<Username>\AppData\Roaming\UiPath\authentication

cheers

1 Like
6

Searching the forum often finds the answer.

1 Like
7

Thank you for the prompt replies @vinitha_yachamaneni , @Anil_G , @postwick

1 Like
8

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.