#Get-NcLdapConfig doesn't return Client Config

1 messages · Page 1 of 1 (latest)

potent heath
#

Hey all,
I’m seeing that when I run Get-NcLdapConfig using the PowerShell toolkit (versions 9.15.1.2410 and 9.16.1.2501), the Client Config field is empty-yet the CLI shows the correct config name. I’ve checked this on multiple clusters running Ontap 9.10 and 9.11. Any insights?

plush coyote
#

have you tried with -zapicall:$true? This is usually my go-to workaround when some fields are not properly populated 🙂

#

I just tested it, for me the Get-NcLdapConfig commandlet works fine in both REST and ONTAPI, but the Get-NcLdapClient commandlet for example only returns the client names via ONTAPI, and not via REST

#

It's rather annoying as you have to piece together stuff from multiple different sources to work around REST/ONTAPI limitations but there's not much that can be done I guess 🙂

#

Example: the REST call gives you the LDAP server IPs, but not the client name and query timeout. The ONTAPI call gives you those two, but omits the LDAP server IP 🤡

image.png