IDE Services LDAP Authentication Fails After Bind Account Password Change

Problem

Users are unable to log in to JetBrains IDE Services or obtain licenses through License Vault.

The server logs may contain LDAP authentication errors similar to:

LDAP: error code 49
AcceptSecurityContext error, data 52e

Cause

IDE Services uses the LDAP Search and Bind authentication method. A configured bind account is first used to connect to LDAP and search for the user.

The issue occurs when the LDAP bind account credentials configured in IDE Services are no longer accepted by the LDAP/Active Directory server. This can happen, for example, after the bind account password has been changed, but the IDE Services configuration has not been updated or the service has not been restarted after the change.

Resolution

1. Verify the LDAP bind account configured in application.yaml:

tbe:
  auth:
    ldap:
      bind-user-login: '<bind-account-DN>'
      bind-user-password: '<bind-account-password>'

2. Confirm that:
   • The bind account is active.
   • The password has not expired.
   • bind-user-password matches the current password of the LDAP bind account.
3. If the password was updated in application.yaml, restart IDE Services so the updated configuration is applied.

For a systemd deployment using ide-services.service:

systemctl restart ide-services.service
systemctl status ide-services.service

4. Retry the login.

Reference

JetBrains IDE Services LDAP configuration — Bind account settings: https://www.jetbrains.com/help/ide-services/ldap.html#specify-bind-account-settings