Skip to main content
Question

Control Room OAuth Connection


Forum|alt.badge.img+1

Hello,

I am attempting to create an OAuth Connection to Outlook in my AA Control Room. I’ve tried to follow the KB article, and believe I have all the correct information such as tenant id, client id, and client secret for Outlook, but when clicking ‘Test Connection’, I’m getting the following error saying that no reply address is registered for the application. I went into the Control Room app registration and added the callback URL as a redirect URI for the control room, but still getting this same error.
 

 

2 replies

madhu subbegowda
Most Valuable Pathfinder
Forum|alt.badge.img+8

@ARolls ,

 

I can see from your screenshot that you're encountering an error when trying to set up an OAuth connection to Outlook in Automation Anywhere Control Room. The specific error is:

AADSTS500113: No reply address is registered for the application.

This is a common Azure AD authentication error that occurs when the redirect URI (callback URL) hasn't been properly configured in your Azure application registration. Here's how to fix this:

  1. Verify your Azure App Registration configuration:
    • Go to the Azure Portal → Azure Active Directory → App registrations
    • Find and select your application
    • Go to "Authentication" tab
    • Under "Redirect URIs", ensure you've added the exact callback URL from Automation Anywhere
  2. Check the callback URL format:
    • The callback URL from AA Control Room should look something like: https://[your-control-room-url]/v1/authentication/oauth2/callback
    • Make sure there are no typos or trailing slashes that don't match
  3. Ensure you're using the correct application:
    • Verify that the Client ID you're using in AA matches the Application (client) ID in Azure
    • Sometimes organizations have multiple similar app registrations
  4. Check URI type:
    • Ensure the redirect URI is registered as a "Web" platform type, not "Mobile and desktop"
  5. Permissions and consent:
    • Verify that you've granted the necessary Microsoft Graph API permissions
    • Check if admin consent has been provided if required
  6. Try clearing your browser cache:
    • Sometimes cached authentication tokens can cause issues

If you continue having problems, you might need to check with your Azure administrator to ensure:

  1. The app registration has the proper API permissions
  2. Your account has sufficient permissions to use the application
  3. The tenant settings allow the authentication flow you're trying to use

Forum|alt.badge.img+1
  • Author
  • Cadet | Tier 2
  • 1 reply
  • March 24, 2025

Thank you for the reply! This successfully fixed the error I was receiving. However, now after clicking ‘Test Connection’, it redirects back to the Control Room page as expected, but it says “Test connection failed”. Would this likely be a permissions issue?


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings