1 前言

一个问题，一篇文章，一出故事。
笔者最近有个任务，通过Token测试LDAP连接是否正常，于是想到通过KeyCloak数据库收集测试所需的参数。

2 最佳实践

2.1 查询REALM设置

select ID,NAME from REALM;

可见如下显示，

+--------------------------------------+-------------------+
| ID                                   | NAME              |
+--------------------------------------+-------------------+
| bc7e68b0-853c-487d-99fb-060b18ac35d7 | master            |
| 73aa50b2-210d-45b4-9e4e-fbf9f428120b | cmdschoolConnect  |
| e5ce9184-1634-4a54-9b92-451376538d8d | cmdschoolSAEGroup |
+--------------------------------------+-------------------+
3 rows in set (0.000 sec)

2.2 查询PROVIDER设置

select ID,NAME from COMPONENT where PROVIDER_TYPE = "org.keycloak.storage.UserStorageProvider" and REALM_ID = "73aa50b2-210d-45b4-9e4e-fbf9f428120b";

可见如下显示，

+------------------------+----------------------+
| ID                     | NAME                 |
+------------------------+----------------------+
| 0tOz4T8ySP-VB9wVjz1eLw | 5_ldap_cmdschool.org |
| i62XHxKwT9qL0wldlGpiww | 8_ldap_cmdschool.com |
| tjmXMm6GTCmNXeBOEyEhpQ | 2_ldap_cmdschool.net |
+------------------------+----------------------+
3 rows in set (0.001 sec)

2.3 查询PROVIDER的参数

select name,value from COMPONENT_CONFIG where (name="connectionUrl" or name="bindDn" or name="bindCredential") and COMPONENT_ID = "tjmXMm6GTCmNXeBOEyEhpQ";

可见如下显示，

+----------------+------------------------------------------+
| NAME           | VALUE                                    |
+----------------+------------------------------------------+
| connectionUrl  | ldaps://cmdschool.org:636                |
| bindCredential | keycloakPassword                         |
| bindDn         | CN=Keycloak,CN=Users,DC=cmdschool,DC=org |
+----------------+------------------------------------------+
3 rows in set (0.000 sec)