Change user auth method from LDAP to RADIUS in the PrvateArkclient generates err:ITATS692E.We see in trace log that Certfingerprint AD prop has long value.vault cannot handle values that exceed 40 char.please provide the steps how to shorten the LDAP pro

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

Change user auth method from LDAP to RADIUS in the PrvateArkclient generates err:ITATS692E.We see in trace log that Certfingerprint AD prop has long value.vault cannot handle values that exceed 40 char.please provide the steps how to shorten the LDAP pro

L1 Bithead
12 REPLIES 12

L3 Networker

I believed that you had id a initial integration with LDAP and added 3 initial group (Vault Admin,Auditor,User). Did you change the auth method from the group level or from individual user level from PrivateArkclient?

 

 

L4 Transporter

You need to contact CyberArk Support. They'll give you a script with instructions to modify the Auth type to RADIUS for existing users. For the new ones you need to set that in the user template of Directory Mapping.

L1 Bithead

Yes, during the initial integration we added the 3 groups with LDAP.

I tried to change the auth method on user level from Privatearkclient

L3 Networker

You can try changing the auth method on group level instead of user level. As i had faced the same issue with you. The step i took to resolve the issue will be

 

  1. Remove all LDAP user ID in Privateark client
  2. Change auth method for 3 groups from LDAP to RADIUS auth
  3. Ask user to login using RADIUS

 

And it work.

 

If this still cant resolve the issue you will need to use PACLI to resolve your issue

L4 Transporter

@RUI WEI NG​  But this way all the users will the access to safes. Though they'll be created back without any additional effort. @Moiez Mohammed​ 

L3 Networker

@Pranav Chugh​ What i did was to create more group in AD. And i will mapped these groups to their respective safe . Did you use PACLI command in this type of situation?

L3 Networker

Change the group template in Private ark to Default Auth Type Radius for the appropriate groups. Delete the LDAP users from Private Ark. Users will be recreated on first logon

L1 Bithead

Hi Mohammed,

 

This is a known issue. The Vault wont be able to handle the operation (change from LDAP to RADIUS), if there is any LDAP property which contains:

  1. Value types not supported by the Vault (special characters)
  2. A value that is more than 40 characters in length.

 

If you have a look at solution 00004020, the CertFingerPrint property has a value that exceeds 40 characters in length - and the associated AD user probably has a cert in the AD properties.

 

The usual solution:

In AD, shorten or remove any LDAP properties which contain special characters and/or are over 40 characters in length. Then delete the user from 'Tools -> Administrative Tools -> Users and Groups' (PAClient) and have them log in again (or try a failed logon attempt if you're allowed to, just to re-provision the user back in the PAClient list). This will cause them to be re-provisioned without the problematic value.

 

Hope, this helps.

L4 Transporter

You can update using PACLI as a workaround. Sample below:

 

pacli init pacli define vault="vault" address="10.10.10.10" pacli logon vault="vault" user="administrator" password="Cyberark1" pacli updateuser vault="vault" user="administrator" destuser="andyg" authtype=RADIUS_AUTH pacli logoff vault="vault" user="administrator" pacli term

 

L1 Bithead

I am trying to do something similar, update auth type on external users (AD users) from LDAP to Radius.

 

I ran the PACLI script and am getting this error:

 

ITATS003E User or Group '12345' has not been defined.

 

If I run it against an internal CyberArk user it runs fine.

L1 Bithead

Never mind, I was using ' instead of ", success!

 

But How do I revert to LDAP, if i Give LDAP_AUTH, I am getting parse error

  • 961 Views
  • 12 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!