Idira Remote Access: Why we got 401 error when using the access token?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Remote Access Articles
1 min read
L2 Linker
No ratings

Question

We successfully got the access token via API but we got a 401 error when using it. Here is the example, we got the token without an error. 
ka32J000000LS6YQAW__eid=ka32J000000LS6Y&feoid=00N2J000009R3kr&refid=0EM2J000003JvDh.png
However, when we tried to launch other calls, we got 401 errors.
ka32J000000LS6YQAW__eid=ka32J000000LS6Y&feoid=00N2J000009R3kr&refid=0EM2J000003JvDm.png

The access token does not seem to work. 

Answer

401 means Unauthorized. It will be triggered when:
- The request requires user authentication.
- Your session has expired and your user has been disconnected

You can find more details from the online page below. 
https://docs.cyberark.com/Product-Doc/OnlineHelp/Alero/Latest/en/Content/WebServices/WebServicesIntro.htm

In your case, you used "https://auth.alero.eu/auth" to authenticate and got access_token. However, you called the "https://api.alero.io/" to process the second step. This URL is pointing to the US data center. If you are using an EU data center, please use "api.alero.eu" instead.

Please also kindly refer to the following page. it stated we have different suffixes for the various data center.
> To call an Remote Access API from the EU data center, make sure the suffix in the URL is .eu. For example, api.alero.eu.
https://docs.cyberark.com/Product-Doc/OnlineHelp/Alero/Latest/en/Content/WebServices/WebServicesIntro.htm
Rate this article:
  • 4990 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎11-05-2026 12:09 PM
Updated by: