Why would a user receive 401 errors on Firefox & Edge getting to <tenantID>.id.cyberark.cloud/my but not in Chrome?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Why would a user receive 401 errors on Firefox & Edge getting to <tenantID>.id.cyberark.cloud/my but not in Chrome?

L3 Networker

We have a single user that is experiencing a strange issue wherein they are faced with a "401 You do not have access to this content" when trying to get to their /My portal in Identity. This user IS licensed and has all of the same group mappings as their co-workers. I cannot find any logs of the 401s. Furthermore, this issue only happens when using Firefox or Edge...Google Chrome is unimpacted and they are able to navigate to all of their CyberArk products without issue.

 

What could be causing this??

4 REPLIES 4

L7 Applicator

https://docs.cyberark.com/identity/latest/en/content/userportal/browser-extension-troubleshooting.htm

Good morning,

 

How does that article pertain to the user in the post? I am sorry if I was unclear, but the user in question is not leveraging the Browser extension for CyberArk Identity. He is simply trying to access his CyberArk /My resources from his web browser and receiving 401 errors.

L4 Transporter

Hi @Tyler Sell​ 

 

As the community has not yet provided an answer to this question for some time, were you able to find a solution?

If so, we'd appreciate it if you could share it.

Your solution could help other community members who have similar questions.

 

Thanks, Liad.

The only solution I was given by support was to add our SSO provider's domain as a trusted domain for our Identity API settings. While this DID fix the issue, I wish that it hadn't. Our other users have been using our SSO service to log in on all browsers just fine for a while now without the change in place. The fact that this user suddenly needed this setting enabled is suspicious and doesn't help me to understand what exactly was taking place. The user's browser was up-to-date, had no extensions installed which would interfere with logins, and was abiding by all Identity authentication policy rules.

 

The problem has gone away at this point though.

  • 384 Views
  • 4 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!