TANDBERG Border Controller User Manual
objectClass: h323Identity
objectClass: h235Identity
commUniqueId: comm1
h323IdentitydialedDigits: 626262
h235IdentityEndpointID: meetingroom1
h235IdentityPassword: mypassword
Add the ldif file to the server using the command:
ldifde
This will add a single H.323 endpoint with an H.323 Id alias of MeetingRoom1 and an E.164 alias of 626262. The entry also has H.235 credentials of id meetingroom1 and password mypassword which are used during authentication.
B.1.3 Securing with TLS
To enable Active Directory to use TLS, you must request and install a certificate on the Active Directory server. The certificate must meet the following requirements:
•Be located in the Local Computer’s Personal certificate store. This can be seen using the Certificates MMC snap in.
•Have the private details on how to obtain a key associated for use with it stored locally. When viewing the certificate you should see a message saying “You have a private key that corresponds to this certificate”.
•Have a private key that does not have strong private key protection enabled. This is an attribute that can be added to a key request.
•The Enhanced Key Usage extension includes the Server Authentication object identifier, again this forms part of the key request.
•Issued by a CA that both the domain controller and the client trust.
•Include the Active Directory fully qualified domain name of the domain controller in the common name in the subject field and/or the DNS entry in the subject alternative name extension.
B.2 OpenLDAP
B.2.1 Prerequisites
These instructions assume that an OpenLDAP server has already been installed. For details on installing OpenLDAP see the documentation at http://www.openldap.org.
The following examples use a standard OpenLDAP installation on the Linux platform. For installations on other platforms the location of the OpenLDAP configuration files may be different. See the OpenLDAP installation documentation for details.
68
