Error: user cannot be added as Safe member because they are not assigned to any Privilege Cloud Role

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

Error: user cannot be added as Safe member because they are not assigned to any Privilege Cloud Role

L2 Linker

Hi,

The corresponding user is member of the AD group mentioned in the mapping in Identity administration portal

 

Field_Content_versions_oct20__0682J00000Ov1N1QAJ.png 

When trying to add the user as a safe member, getting this error :

 

Field_Content_versions_oct20__0682J00000Ov1LuQAJ.png 

When putting the user account directly in the privilege cloud users group, it works ok.

 

I've tried other users member of this AD group, worked fine.

 

But keep getting error for this particular user... (I've double checked several times, he's definitely member of the AD group that is mapped, so no issue there)

 

Any ideas?

 

Thank you

14 REPLIES 14

L6 Presenter

Hello,

 

This is an interesting situation since almost everything works with the exception of this one user's group membership. I might try deleting the user account from CyberArk Identity and having them log in again to pull a fresh user profile from Active Directory.

 

How are you pulling group membership in Identity, is it through the Identity Connector to Active Directory? You can confirm this in Identity Administration in Settings > Network. If you are using the Identity connector, does it appear that any of the 'enabled services' of the connector have been removed? I believe the default services are {AD Proxy, API Proxy Service, App Gateway, LDAP Proxy, RADIUS server, Web Server (IWA), Win Net Proxy Service}.

L2 Linker

Hi Jah,

" I might try deleting the user account from CyberArk Identity and having them log in again to pull a fresh user profile from Active Directory."

-> the user is not in identity (never logged in) ; we are in the process of migrating from onprem to pcloud, so recreating safes, accounts etc on pcloud using api

We have some individual safes (on which we put the user as member directly), the error we are facing here is for this kind

 

We don't want to have to ask users to login to identity beforehand ; maybe this will work but it would be kind of a 'workaround', we want to have it work like the others

 

We are using identity connectors, all are actives, and the services are enabled (including the ones you mentioned)

I've already checked if it was maybe a refresh issue, but the config in the connectors is at 10 minutes ..

 

Was able to find someone to test on a pcloud lab, it worked fine (just needed to wait for a while -- prob because of this 10 minutes setting) ; but in the end, it worked OK

 

Here it's been several days already, still failing this morning

 

The only difference I see (compare to the lab testing) : as I've mentioned earlier, for this process we are using API calls, so the first error happened through an API call

In the lab, everything was done directly through pcloud portal..

 

By the way, I've changed the AD group of this user today to a different one (license issue) ; a new AD group that is mapped under one of the privilege cloud of course

Still KO (just retried now), so even this new AD definition update didn't change anything!

 

Any ideas?

Thank you

L6 Presenter

In this case I might consider having the individual user log in as a workaround. I'm not 100% sure why this is the case, but sometimes I have difficulty adding safe members before that safe member has logged in even though it usually works for most users.

L2 Linker

Hi,

Well we might end up doing that, I'll let you know

In any case, since it also happens on your side sometimes, might be something CyberArk should look into on the tech side!

L0 Member

So what AD is this - On-Prem or Azure ?

L1 Bithead

So what AD is this - On-Prem or Azure ?

On prem

L1 Bithead

I have faced this issue nd what i did is, select the user object > go to actions menu and click Reload Rights option. You may have to repeat this step one or tow times. Then you can go to the user properties > Roles and you will see "Privilege Cloud Users " assigned.

Is the user a part of more than one AD group (than this group in question) that are added to other safes ?

Is the user a part of more than one AD group (than this group in question) that are added to other safes ?

L1 Bithead

Did you ever raise a case for this and get a solution from CyberArk?

L2 Linker

It was perhaps related to the fact that we have big domain, so the cyberark connector was taking lots of time to detect the changes in our environment.

 

We did some optimization by tweaking some registry keys, making it work in the end

It will likely be a large environment and the Identity connector having delays when searching for users.

Log a case, they will probably point you to https://community.cyberark.com/s/article/CyberArk-Identity-How-to-configure-restricted-or-preferred-domain-controller-lookups-for-the-CyberArk-Identity-Connector

 

However, implement with care as I had to roll this back due to some unintended problems.

Out of interest, this KB? https://community.cyberark.com/s/article/CyberArk-Identity-How-to-configure-or-restrict-attribute-matching-for-the-CyberArk-Identity-Connector

Or did you implement something like https://community.cyberark.com/s/article/CyberArk-Identity-How-to-configure-or-restrict-attribute-matching-for-the-CyberArk-Identity-Connector

  • 2087 Views
  • 14 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!