Vendor user provisioning choices

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

Vendor user provisioning choices

L4 Transporter

Hello,

 

Regarding inviting vendors https://docs.cyberark.com/Product-Doc/OnlineHelp/Alero/Latest/en/Content/Admin/InviteVendors.htm

 

Can someone explain a bit more what the exact concrete differences are between the two user provisioning choices ?

Remote Access creates and manages the user - For vendor access to PAM applications, specify the name of the Vault user and the Remote Access VendorLDAP groups that the user will belong to. For more information about VendorLDAP, see Manage groups.

Administer creates and manages the user - The Remote Access admin will create and manage the user for this Vendor.

 

If Remote Access creates and manages the user is chosen it is correct to state that remote access will automatically create an LDAP user in the configured Remote Access VendorLDAP directory and add the LDAP user to the specified LDAP groups ?

The actual creation of the Vault User and the Vault groups isn't done by Remote Access isn't it but is done at Privileged Cloud/PAS level isn't it ? That is, upon first logon to the PVWA Portal the Vault will create the LDAP reference object in the Vault. The Vault administrator will have to map the VendorLDAP groups to the required safes (or via REST API).

 

What happens if "Administrator creates and manages user" is selected instead ?

Does the Remote Access Admin then manually have to create the user in the VendorLDAP directory and add the user manually in the VendorLDAP ?

 

Kr

 

 

8 REPLIES 8

L3 Networker

Hi @Edwin Dhondt​ ,

 

If you choose "Administrator Creates and Manages user" - you will have to go to the vault and create manually the PAS user for this vendor, in the Remote Access portal you will have to mention the username for this vendor.

 

If you choose "Remote Access creates and manages the user" - the user will be created in the Vendor LDAP and automatically in the Vault.

Once you remove the vendor from the Remote Access portal, the identity on the Remote Access portal and in the Vault will be deleted.

 

I hope it answers your question.

BTW, we have a new and updated training that you can take, the vendor provisioning is one of the topics there.

 

Thanks

Guy

Hello Guy, Many thanks. Is this a self-paced training ? Can you provide me the link (or name) to the updated version ? Can you provide me a screenshot of the options that become available when choosing “Admin will create and manage the vault user”. That might make things more clearer to me. In the Remote Access InstallConfigure self-paced training I ran through a couple of weeks ago the following is mentioned when selecting “Remote access will create and manage the vault user” option: “By selecting the Remote Access will create and manage the Vault user option, the Vendor user will be created in the VendorLDAP upon accepting the invite. The integration and directory mapping between the Vault and the VendorLDAP, allows the Vendor user to be transparently created in the Vault when they first try to authenticate to the application (thus, achieving "Just-in-time" provisioning).” According to the above, in my understanding Remote Access will create the user in the VendorLDAP directory (and add the user to the required groups in the VendorLDAP directory), but it’s the Vault (PAS or Privilege Cloud) that will create the Vault User upon first login of that user to the PVWA, not Remote Access. Isn’t it ? If correct then your answer seems to contradict this ? If you choose “Administrator Creates and Manages user”. Will Remote Access still create the user in the VendorLDAP directory and make the user a member of the required VendorLDAP groups in that directory? If the Administrator forgets to create the Vault User, what will happen ? Won’t the VendorLDAP directory mapping in the vault, upon first login of that user, fetch the user details and create an External Vault User object in the vault, referencing the LDAP user ? What am I missing ? Kr

L3 Networker

Hi Kr,

 

It's CyberArk Vendor PAM (Remote Access) Administration.

When you choose the option of "Admin will create..." - you just have one field, there you should mention the username in the Vault.

 

VendorLDAP is just another LDAP source to the vault, any user \ group created in this directory, will be mapped to the vault.

In Privilege Cloud, we don't have the directory (since we also don't have the connector). Therefore, any user or group added in the Remote Access portal, will be created directly in the Vault as an EPV user.

 

In VendorLDAP, the user will be created in the Vault after the first login, but in Privilege Cloud, the users and groups will be created automatically right after they are added to the Remote Access portal.

 

If you choose Administrator Creates and Manage user, you have to mention the username in the Remote Access portal. If you don't create the user in the Vault, you will get an error message that this user doesn't exist in the Vault (PVWA error message).

 

I hope my answer helps.

 

Thanks

Guy

Hi Guy, Do you mean that in a setup where Remote Access Vendor Mgt is combined with Privilege Cloud * There's no VendorLDAP directory ? * The users and groups created in Remote Access Vendor Mgt are not provisioned to a VendorLDAP directory ? * The users and groups created in Remote Access Vendor Mgt are instead created immediately in the Privilege Cloud Vault as CyberArk internal users and groups, so not as LDAP reference objects to users/groups in VendorLDAP ? If that's correct, * Why is a different approach used (no Remote Access Connector and therefore no VendorLDAP directory created in Privilege Cloud) ? * Are there any plans to also support VendorLDAP in a Remote Access + CPC SaaS combination and by when ? * How does Remote Access Portal connect to Privilege Cloud and to which component, if there's no connector and VendorLDAP ? * If groups were created in Remote Portal and assuming no VendorLDAP is available in combination with Privilege Cloud, where are the created groups then stored ? If we invite vendors can we select from groups created earlier ? * JIT Vendor Mgt is support in Remote Access and Privilege Cloud combination isn't it ? Kr

In Privilege Cloud:

  • There is no Vendor LDAP
  • Users and Groups are provisioned directly to the Vault by using API calls (it works behind the scenes, nothing should be configured manually)
  • They are created as Internal Users and Groups, not as LDAP references as you mentioned.
  • JIT works differently, we will add \ remove the users if they're deleted or deactivated from the Remote Access portal.

 

I think that it might be better to have a call instead of this long thread.

Do you work with someone from CYBR?

 

Hi, When do you have a slot available ? I’m available right now. Ok ? If not can you provide a slot (Belgian time). Only pre-sales contact for the moment. Kr, Edwin

Hey,

 

Send me an email: [email protected]

Mail has been sent (I included ms team invite)
  • 702 Views
  • 8 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!