Introduction

Starting with Gurobi 9.5, we have enabled the Cluster Manager to integrate with the access management protocol LDAP. However, enabling LDAP may influence already existing accounts in your Cluster Manager setup

What will happen?

The accounts will be disabled only if they are not found in the LDAP using the username. If the username is the same in LDAP and Cluster Manager, the user account will still be active, just that the password will be the one form LDAP, API keys are unchanged. Before activating the LDAP, you can rename the username of a user in the Cluster Manager. You can also rename a user after activating the LDAP, and it will be reenabled if it is found later on.

To test this process, you can start a cluster manager with a new database and test the integration, there is no need for a license. In order to get familiar with this process, you can start a 9.5.0 (or later) cluster manager on a copy of the main database, then activate LDAP, the goal being to test access to accounts, not running optimization, so no need to connect compute server nodes.

You can find more information about upgrading an existing installation of Gurobi Remote Services in the Upgrading an Existing Installation section of the documentation.

Note: You can always  still log in as sysadmin even after LDAP binding, as a "System Administrator log in" link will be added at the login page