This property is supported only on systems that use DIGEST-MD5 binding. For systems that use simple binding with SSL or TLS protection, see LdapClientTlsRandFile.
The DIGEST-MD5 authentication protocol used by LDAP is deprecated. Teradata strongly recommends you use simple binding with TLS protection, and stop using DIGEST-MD5.
The LdapClientRandomDevice property specifies a device, FIFO, or pipe that provides random bits when the default random number generator, for example /dev/[u]random on Linux, is not available, or if another random number generator is preferred.
Default Property Value
The default setting is "", that is, no device, FIFO, or pipe is specified.
Valid Settings
| Setting | Description |
|---|---|
| "" | No random number generator is specified. The system uses the default random number generator for the operating system. |
| A file name | Specifies a device, FIFO, or pipe that provides random bits. |
Editing Guidelines
- To set a value, you must manually add this property to the TDGSS configuration file for the needed mechanisms. See About Editing Configuration Files.
- Edit this property on the database and on Unity, if used. Also see Coordinating Mechanism Property Values for Unity.
- Use the default setting, if possible. Specify a value for the LdapClientTlsRandFile only when the default random number generator) is not available, or if you want to use another random number generator.
- If the default is not available, you can install a copy of EGD or PRNGD every node, to provide a random number generator, and set the value of this property to the name of the EGD or PRNGD socket.The installed copy of EGD or PRNGD must have the same name on all Vantage nodes. See the EGD or PRNGD Readme file for details.