We have had issues where users have tried to delete entries in the Identity Sources > LDAP Connections and have received an error message.
It has not been clear what is causing the error. However as a work around, if the customer is competent with MySQL commands, we can send them the following fix.
This is a two-stage process. The first stage you will delete the corresponding ldap entry. The second stage you need to re-index the remaining entries.
When you are logged into MySQL please follow these instructions:
select * from ldap_server_connection;
You will get results similar to the example below except it will show your ldap entries:
Now as an example I want to remove the entry corresponding with id number 9. (circled in blue)
delete from ldap_server_connection where id = 9; (You would obviously use the id that corresponds with the entry you wish to delete on your system)
Then if you run the select * from ldap_server_connection; again, you will notice the entry has been deleted:
But there is a new problem here because the index numbers (Circled in Red) are now out of sequence. We are missing number 2. So, you need to re-index the table.
To do this, we use the following command
Update ldap_server_connection set ldap_server_connections_idx = ldap_server_connections_idx – 1 where ldap_server_connections_idx > #
(replacing the # with the index number that has been deleted)
So for my example index number 2 has been deleted, so I type in
Update ldap_server_connection set ldap_server_connections_idx = ldap_server_connections_idx – 1 where ldap_server_connections_idx > 2;
And then if we run the select * from command again you can see the index numbers are back in order.
You then need to restart the DualShield Server service.