Creating LDAP Entries for OpenAccess SDK Services
- Last Updated: May 12, 2026
- 1 minute read
- OpenAccess SDK
- Version 8.1
- Documentation
If you are using LDAP directories to store connection information for OpenAccess SDK services, you must create a single LDAP directory entry for each service and identify that LDAP directory entry by a Distinguished Name (DN). The LDAP entry must contain the TCP/IP host name of the OpenAccess SDK Server and the TCP/IP port on which the OpenAccess SDK Server is listening. Optionally, the LDAP entry can contain a server data source to use for the connection to the OpenAccess SDK Server. If a server data source is not specified, the client uses the default data source.
The following table shows an example of an LDAP directory entry and attributes you may want to store in an LDAP entry for an OpenAccess SDK service. All attributes use cis syntax.
Example: LDAP Directory Entry for an OpenAccess SDK Service
| Attribute | Description | Example | Required? |
| OpenAccessHost | Specifies the TCP/IP host name or the TCP/IP address on which the OpenAccess SDK Server is running. | myhost.mycompany 10.131.70.152 | Yes |
| OpenAccessEncrypted | Uses SSL encryption. | 1 | No |
| OpenAccessCustom Properties | Passes custom connection properties directly to the IP layer. | A=abc;B=xyz | No |
| OpenAccessPort | Specifies the TCP/IP port on which the OpenAccess SDK Server is listening. | 19986 | Yes |
| ServerDataSource | Specifies the server data source to use for the connection. | Sales | No |
How you create LDAP entries depends on the LDAP product you are using. For instructions on creating LDAP entries, refer to your LDAP product documentation.