AudioCodes SBC/Gateway login – LDAP / LDAPs authentication

The authentication of the login on the AudioCodes can be done via LDAP. This makes it possible to map different authorization structures on the AudioCodes. Another advantage is that it is possible to see in the syslog which administrator has made which changes, so that changes are traceable.

In the first step, we activate LDAP authentication on the AudioCodes. We also set the „Use Local Users Database“ parameter to „Always“. This means that local access is still available if the LDAP server is not available.

The lightning behind the parameter indicates that the SBC must be restarted. Furthermore, the LDAP service must be activated under the LDAP Settings (SETUP -> IP Network -> RADIUS & LDAP -> LDAP Settings).

After restarting the SBC, the following group is automatically created. We now create a management group for access.

Now the LDAP server is created. For the LDAP Password insert only the $ character, so that the variable is transferred accordingly. As „LDAP BIND DN“ the value $ is entered. The connection status „LDAP_CONNECTION_BROKEN“ is normal, the connection is only established for a short time during login. Of course we use TLS, so that the data is transferred encrypted.

The Search Base DN is created so that the administrator accounts are readable.

Die AD-Gruppe mit dem Namen AudioCodes_Security_admin wurde erstellt und mit den Mitgliedern gefüllt. Das Level „Security Admin“ beinhaltet alle Konfigurationsmöglichkeiten.

Now, if the Activity Log is enabled in AudioCodes, we can track logins in the syslog.

11:11:31.431  local0.notice  [S=1391492] [BID=5977e8:6]  Activity Log: WEB: Successful login at User: adm-mrose. Session: WEB ( [Time:08-02@11:11:30.635]

Changes are presented as follows.

11:19:40.868  local0.notice  [S=1394667] [BID=5977e8:6]  Activity Log: IP Profiles row 5 - 'Symmetric MKI' was changed to '0'. User: adm-mrose. Session: WEB ( [Time:08-02@11:19:39.076]
11:19:40.868  local0.notice  [S=1394668] [BID=5977e8:6]  (N  1163890) IPProfileChangeEvent: (#0) -> (#0)Core [Time:08-02@11:19:39.077]

Das könnte dich auch interessieren …

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht.