#With REST,ldap client config name has been created as vserver name by default,can this be enhanced?

1 messages · Page 1 of 1 (latest)

echo bolt
#

We were able to create a custom ldap client config name with ZAPI, but with REST , by default it's taking the vserver name as ldap client config name and no way to customize it.. We would need the ldap client config name as same as ldap client config created on ldap Linux server. Can this be enhanced in future REST versions?

dire canopy
#

You must be doing something incorrectly. I am able to create any number of client config names via Rest. Also, your Linux server has no visibility to the name of your config name. Perhaps you are talking about the nfs4 id domain.

echo bolt