Verify Directory Virtual Directory
The Verify Directory Virtual Directory image can be used to run an advanced proxy that can aggregate identity data across LDAP directories from different vendors to create a single point of access.
- Location
- The proxy image is hosted in an IBM Cloud Repository, and can be accessed at:
icr.io/isvd/verify-directory-virtualdir:<tag>. For example, to pull the more
recently released image in a Docker environment:
docker pull icr.io/isvd/verify-directory-virtualdir:latest - Configuration
- The configuration of a virtual directory container can either be supplied in a YAML configuration file, or can be specified by using environment variables. Details on the format of the configuration can be found in the Configuration Format topic, and the list of supported configuration entries can be found in the YAML Specification.
- Environment Variables
- The following environment variables are used by the container.
Table 1. Environment Variables Name Description LANG Specifies the language in which log messages are to be displayed. The list of supported languages can be found in the Language Support topic. If the LANG environment variable is not set the container displays messages in English. YAML_CONFIG_FILE The full path name to the YAML configuration file that is to be used to configure the container. This configuration file must be available in the container file system, and must be accessible by the user that the container is running as. yaml-configuration-entry It is possible to set individual proxy configuration entries by using environment variables. The name of the environment variable must match a normalized version of a YAML configuration entry name. Further information can be found in the Environment Variables topic. - Persistence
- In most situations, the virtual directory container is stateless and does not require any
persistent storage. The exception is if a schema is modified after the container is started, by
using an LDAP modify operation after the container starts. In this situation, the modified schema
files are stored in the
'/var/isvd/data'path of the container. This path is mounted in the container as a persistent volume so that the modified schema files are not lost when the container is restarted. - Service
- The container, by default, listens for incoming requests on port 9636. Use the
general.ports.ldapsandgeneral.ports.ldapconfiguration entries to change the ports on which the container listens. - Licensing
- The image is covered by the IBM® Security Verify
Directory
Standard license. The license can be viewed directly from the image by running the
following command in a Docker environment:
docker run --rm icr.io/isvd/verify-directory-virtualdir:latest license standard - Image Tags
- The following image tags are supported by the image.
Table 2. Image Tags Tag Description latestThe most recently released version. V.R.M.FA particular release, of the format {version}.{release}.{modfication}.{fixpack}. For example, 10.0.1.0.