- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
03-08-2023 02:37 AM
Hi,
The corresponding user is member of the AD group mentioned in the mapping in Identity administration portal
When trying to add the user as a safe member, getting this error :
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
03-13-2023 09:56 AM
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}.
03-13-2023 10:19 AM
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
03-13-2023 10:26 AM
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.
05-03-2023 12:03 PM
So what AD is this - On-Prem or Azure ?
05-03-2023 12:03 PM
So what AD is this - On-Prem or Azure ?
05-04-2023 04:01 AM
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.
05-04-2023 08:26 AM
Is the user a part of more than one AD group (than this group in question) that are added to other safes ?
05-04-2023 08:26 AM
Is the user a part of more than one AD group (than this group in question) that are added to other safes ?
03-07-2024 11:48 PM
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
03-08-2024 02:03 AM
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.
03-08-2024 02:04 AM
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
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!

