PowerFlex LDAP authentication fails when using a third-party multi-factor authentication (MFA) for Active Directory (AD).

Summary: PowerFlex LDAP authentication fails when using a third-party multi-factor authentication (MFA) for Active Directory. Third-party balancers might obstruct LDAP traffic causing LDAP logins to fail. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

  • Failed Authentication Attempts: Users cannot authenticate in PowerFlex using LDAP credentials.
  • No Issues with Direct AD Authentication: Users might be able to authenticate directly with Active Directory without any issues, but the problem arises when they use LDAP through PowerFlex.

Primary MDM (PMDM) trc log would show similar outputs like this:

2023/09/15 16:34:12.881368 7f0159dccdb0:mosEventLog_PostInternal:00609: New event added. Message: "Command login received, User: 'a172001'. [20874]". Additional info: ". Originating source IP: 127.0.0.1" Severity: Info
2023/09/15 16:34:12.881377 7f0159dccdb0:ldapAuthMgr_GetLdapServiceRefByKey:02371: Failed to get LDAP service object by name - rc: LDAP_SERVICE_NOT_FOUND
2023/09/15 16:34:12.881425 7f0159dccdb0:ldapAuthMgr_GetAuthorizerPassword:00268: password-len: 9, rc: 65
2023/09/15 16:34:12.881481 71d000003655:mosOsThrd_StartFunc:00576: Starting thread () tid 13909
2023/09/15 16:34:12.881591 71d000003655:mosLdap_InitConnection:00205: Connection was successfully established to ldaps://14.14.14.33:636 ldap service
2023/09/15 16:34:13.003621 71d000003655:mosLdap_Bind:00130: After ldap_sasl_bind - rc: 0, msg-id: 1
2023/09/15 16:34:13.045002 71d000003655:mosLdap_ParseBindResult:00218: ldap_sasl_bind: Invalid credentials (49)
2023/09/15 16:34:13.045010 71d000003655:mosLdap_ParseBindResult:00225: Additional information: 80090308: LdapErr: DSID-0C090447, comment: AcceptSecurityContext error, data 52e, v3839
2023/09/15 16:34:13.045014 71d000003655:mosLdap_Bind:00178: Failed to bind to ldap service with username a172001
2023/09/15 16:34:13.045180 71d000003655:mosLdap_SearchUserInDomainGroupsIntr:00581: User "a172001" was found in 0 groups - search-user: a172001, bind-user: a172001, rc: LDAP_AUTHENTICATION_FAIL, time: 170 ms
2023/09/15 16:34:13.045220 7f0159dccdb0:ldapAuthMgr_Authenticate:00736: LDAP authentication search for user: a172001 in domain: ldaps://duoproxy.prci.com:636 didn't find any matches (LDAP_AUTHENTICATION_FAIL)
2023/09/15 16:34:13.045247 7f0159dccdb0:mosEventLog_PostInternal:00609: New event added. Message: "Command login was not successful. Error code: User authentication on LDAP service failed. Please check username and password.


When attempting to log in, the output error seen would be similar to what is shown below:

scli --login --username sio@sio.lab --password 'Scaleio123!' --ldap_authentication
Error: MDM failed command. Status: user authentication on LDAP service failed. Please check username and password.

 

Cause

When using PowerFlex for LDAP authentication, third-party balancers might obstruct LDAP traffic.

Resolution

A potential workaround is to point the LDAP authentication directly to the domain controller when creating the LADP service using SCLI. By doing this, you can bypass any potential blockages or issues caused by third-party balancers.

You must delete and re-create the LDAP service to point it directly to the domain controller using SCLI.

Additional Information

Impacted Versions

All PowerFlex Versions

Fixed In Version

N/A

Affected Products

PowerFlex rack, ScaleIO
Article Properties
Article Number: 000218362
Article Type: Solution
Last Modified: 22 May 2025
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.