Adding vendor to Alero

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

Adding vendor to Alero

L1 Bithead

When adding a vendor and under the section "Vault user provisioning for vendor." There are two options: "Alero will create and manage the Vault user" and "Admin will create and manage the vault user."  Whenever selecting the option Alero creating and managing the vault user and assigning the user to a AleroLDAP group when does that user become available to add to a safe? I notice if you choose "Admin will create and manage the user" it's immediate and uses an EPV license. Can they only be added to the safe by AleroLDAP group if managed by Alero, or is there a way to add the individual users name? Or is this a synchronization type of task where it takes time? We had our implementation sync meeting weeks back, but were busy building other parts out of CyberArk. Any help is appreciated!

1 accepted solution

Accepted Solutions

L1 Bithead

@Bernhard Brückler​ @Dmitry Baitman​ I received the solution. Our implementation engineer had escalated it internally at CyberArk. It turns out I found a bug. I set the access expiry date way too far in the future. I had set it to 2100 for testing...From what I learned, if you set it past 2038 it doesn't register properly. I can now search in the vault and find the Alero managed users. Thanks for your responses all! I hope this information can help another customer of CyberArk as well!

 

View solution in original post

7 REPLIES 7

L7 Applicator

The vendor user will consume either a "EPVUser" license or a "ExternalUsers" license, depending on how you create it manually or how the directory mapping is set up. "EPVUser" is the default Vault user type that can do everything, and "ExternalUsers" is a special Vault user type that you can license which is cheaper, but limited in functionality.

 

As soon as you add a vendor in Alero (new name: CyberArk Remote Access) and select "Alero will manage the user", the user is added to the LDAP directory that runs on the Alero connector server. From there, the vendor user will behave like any other user that comes from an external LDAP directory. You'll see the user in your Vaults "Users and Groups" list as soon as the user logs in for the first time *or* you manually search for it (for example in the "Add members" dialogue" of a safe).

L1 Bithead

Summey,

  1. Shadow user object is created for Vendor when he/she scans the 1st QR code presented by the activation link from invite email.
  2. "Admin will create and manage the user" means Vendor already has working login to PVWA and it'll be used instead of Alero LDAP. In other words, this user can login to PVWA directly. And yes, if such user exists - it'll use EPVUser license.
  3. Of course, it's easier to manage permissions to safes based on groups rather than individual users. This is right not just for Alero, but also for regular Cyberark EPV use case.
  4. You can check with your Account Executive reg. different licensing options in case you don't want Alero vendors to use your regular EPVUser licenses.

 

Hope it helps.

 

L1 Bithead

Okay thank you @Bernhard Brückler​ and @Dmitry Baitman​ I am going to do some testing. We definitely don't want our vendors to use our regular EPVUser licenses as we paid for Alero licenses. We currently have a test user with a pending invitation, I'll have the user login for the first time and see if I can see it. Currently when I go to add member on a safe, in the "search in" portion I search in "vault" and not my org's domain and don't see the user yet. Will update once the invitation is accepted Monday. We are using privileged cloud and not an on prem solution, not sure if that matters either. Thank you.

Summey,

The user you're looking for is in Alero LDAP and that's where you should look after invitation is accepted.

But you'll still be able to see shadow user in PAClient and that's how you can verify with what type it's been created. You also can check your licensing report before and after user is created.

L1 Bithead

@Bernhard Brückler​ @Dmitry Baitman​ I received the solution. Our implementation engineer had escalated it internally at CyberArk. It turns out I found a bug. I set the access expiry date way too far in the future. I had set it to 2100 for testing...From what I learned, if you set it past 2038 it doesn't register properly. I can now search in the vault and find the Alero managed users. Thanks for your responses all! I hope this information can help another customer of CyberArk as well!

 

L1 Bithead

Hi,

 

I am facing an issue when invited the external vendor by selecting "Remote Access will create and manage the vault user" and added the group as well. But when the vendor tries to access, he is getting an error:

{"Error code": ITATS894E","Error message":"An unhandled exception has occured."}

 

Thanks,

Roopa

L2 Linker

I also faced the same error in the Lab when the External Vendor try to connect to the PAM url .

 

  • 1 accepted solution
  • 1223 Views
  • 7 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!