VPLEX: When logging in with LDAP user via SSH "Permissions on the password database may be too restrictive"

After completing the configuration of LDAP for VPLEX and logging in using AD account, via SSH, user observed the following message "Permissions on the password database may be too restrictive".



Message appears to only be reported when using LDAP user accounts.
Other than the message, user has no other issues administering the VPLEX.
 

LDAP config details
VPlexcli:/> authentication directory-service show
external-authentication-service: AD
ip: 10.x.x.x
User Search Path: dc=abcgroup,dc=com
connection-type: SSL
Server certificate is configured: No
mapped-principal:
[Groups ]: ['CN=RL VPLEX Admins,OU=Common,OU=Groups,DC=abcgroup,DC=com']

• ldapsearch output

service@hostname:~> ldapsearch -x -LLL -l 30 -H ldap://10.x.x.x:389 -b 'CN=RL VPLEX Admins,OU=Common,OU=Groups,DC=abcgroup,DC=com' -D 'CN=svemcisilon,OU=services,DC=abcgroup,DC=com' -w XXXXXXXXXX -E pr=1000/noprompt
dn: CN=RL VPLEX Admins,OU=Common,OU=Groups,DC=abcgroup,DC=com
objectClass: top
objectClass: group
cn: RL VPLEX Admins
description: VPLEX is now AD-enabled. Group needed in order to add storage administrators for VPLEX administration and management. This group will be mapped to VPLEX management consoles in NA (2 prod and 2 dev systems).
member: CN=admssmith,OU=MA,OU=People,DC=abcgroup,DC=com
member: CN=admbjones,OU=RTP,OU=People,DC=abcgroup,DC=com
member: CN=admjdoe,OU=MA,OU=People,DC=abcgroup,DC=com
distinguishedName: CN=RL VPLEX Admins,OU=Common,OU=Groups,DC=abcgroup,DC=com
instanceType: 4
whenCreated: 20220210134131.0Z
whenChanged: 20220213205448.0Z
uSNCreated: 924908844
uSNChanged: 926986370
name: RL VPLEX Admins
objectGUID:: zwLHqEsazUysXZjpDIP0Og==
objectSid:: AQUAAAAAAAUVAAAAAwAKFqEHe0zBORr+fqgBAA==
sAMAccountName: RL VPLEX Admins
sAMAccountType: 268435456
managedBy: CN=PGedhopeful,OU=MA,OU=People,DC=abcgroup,DC=com
groupType: -2147483640
objectCategory: CN=Group,CN=Schema,CN=Configuration,DC=abcgroup,DC=com
dSCorePropagationData: 16010201000000.0Z

The message is determined to be a cosmetic issue with SLES11.

Engineering has tested for this issue and in the past, it was determined that the message could safely be ignored.