Page created: 4 Feb 2020 |
Page updated: 22 Jul 2020
Directory Server provides the following command-line tools, which you can run in interactive, noninteractive, or script mode.
|Use this option
Information about arguments and subcommands
A list of subcommands
More information about a subcommand
dsconfig list-log-publishers --help
Note: For detailed information and examples of the command-line tools, see the Ping Identity Directory Server Command-Line Tool Reference.
|Perform an internal task that examines all or a subset of entries in the server, writing a series of reports on potential risks with the data. Reports are written to the output directory organized by backend name and audit items.
|Perform repeated authentications against Directory Server, where each authentication consists of a search to find a user followed by a bind to verify the credentials for that user.
|Run full or incremental backups on one or more directory server backends. This tool also supports the use of a properties file to pass predefined command-line arguments. See Saving Options in a File for more information.
|Encode raw data using the base64 algorithm or decode base64-encoded data back to its raw representation.
|Collect and package system information useful in troubleshooting problems. The information is packaged as a zip archive that can be sent to a technical support representative.
|Generate a summary of the configuration changes in a local or remote server instance. The tool can be used to compare configuration settings when troubleshooting issues or when verifying configuration settings on new servers.
|Create a Run Control (RC) script that you can use to start, stop, and restart the Directory Server on UNIX-based systems.
|Create a systemd script to start and stop the Directory Server on Linux-based systems.
|Inspect the contents of Directory Server local DB backends that store their information in Berkeley DB Java Edition databases. Only backends of type local DB can be inspected by this tool.
|Submit a "deliver one-time password" extended request, OID 188.8.131.52.4.1.30184.108.40.206, to the server which results in a the generation of a one-time password that is delivered out-of-band to the specified user. This tool can be used to test the UNBOUNDID-DELIVERED-OTP SASL mechanism.
|Generate and deliver a single-use token to a user through some out-of-band mechanism. The user can provide that token to the password modify extended request in lieu of the user's current password in order to select a new password.
|View and edit the Directory Server configuration.
|Configure the JVM arguments used to run the Directory Server and associated tools. Before launching the command, edit the properties file located in config/java.properties to specify the desired JVM options and JAVA_HOME environment variable.
|Manage data replication between two or more Directory Server instances.
|Obtain a listing of all of the DNs for all entries below a specified base DN in the Directory Server.
|Encode user passwords with a specified storage scheme or determine whether a given clear-text value matches a provided encoded password.
|Encrypt or decrypt data using a key generated from a user-supplied passphrase, a key generated from an encryption settings definition, or a key shared among servers in the topology. The data to be processed can be read from a file or standard input, and the resulting data can be written to a file or standard output. You can use this command to encrypt and subsequently decrypt arbitrary data, or to decrypt encrypted backups, LDIF exports, and log files generated by the server.
|Manage the server encryption settings database.
|Request that the Directory Server enter lockdown mode,
during which it only processes operations requested by users holding the
|Export data from the Directory Server backend in LDIF form.
|Extract changes matching a given set of criteria from a Directory Server audit log so that they can be replayed (for example, as part of a disaster recovery process) or reverted (for example, to back out changes made in error).
|Generate a shared secret that you can use to generate time-based one-time password (TOTP) authentication codes for use in authenticating with the UNBOUNDID-TOTP SASL mechanism or with the validate TOTP password extended operation.
|Identify entries containing one or more attributes that reference entries that do not exist. This might require the ability to perform unindexed searches and/or the ability to use the simple paged results control.
|Identify unique attribute conflicts. The tool can identify values of one or more attributes that are supposed to exist only in a single entry but are found in multiple entries.
|Import LDIF data into the Directory Server backend.
|Parse a provided LDAP filter string and display it a multiline form that makes it easier to understand its hierarchy and embedded components. If possible, it might also simplify the provided filter in certain ways (for example, by removing unnecessary levels of hierarchy, like an AND embedded in an AND).
|Intercept and decode LDAP communication.
|Compare the contents of two LDAP servers.
|Display and query LDAP result codes.
|Perform compare operations in the Directory Server. Compare operations can be used to efficiently determine whether a specified entry has a given value.
|Delete one or more entries from an LDAP directory server. You can provide the DNs of the entries to delete using named arguments, as trailing arguments, from a file, or from standard input. Alternatively, you can identify entries to delete using a search base DN and filter.
|Apply a set of add, delete, modify, and/or modify DN operations to a
directory server. Supply the changes to apply in LDIF format, either from
standard input or from a file specified with the
ldifFile argument. Change records must be separated
by at least one blank line.
|Update the password for a user in an LDAP directory server using the password modify extended operation (as defined in RFC 3062), a standard LDAP modify operation, or an Active Directory-specific modification.
|Process one or more searches in the Directory Server.
|Compare the contents of two files containing LDIF entries. The output is an LDIF file containing the add, delete, and modify change records needed to convert the data in the source LDIF file into the data in the target LDIF file.
|Apply a set of changes (including add, delete, modify, and modify DN operations) to a set of entries contained in an LDIF file. The changes are read from a second file (containing change records rather than entries), and the updated entries are written to a third LDIF file. Unlike ldapmodify, ldifmodify cannot read the changes to apply from standard input.
|Search one or more LDIF files to identify entries matching a given set of criteria.
|Request that the Directory Server leave lockdown mode and resume normal operation.
|List the backends and base DNs configured in Ping Identity Directory Server.
|Load the schema definitions contained in a specified LDIF file into the schema for a running server. You can only use this command with a server instance running on the local system.
|Generate LDIF data based on a definition in a template file. For example template files, see the server's config/MakeLDIF directory. In particular, the examples-of-all-tags.template file shows how to use all of the tags for generating values.
|Retrieve or update information about the current state of a user
account. Processing is performed using the password policy state extended
operation, and you must have the
privilege to use this extended operation.
|Manage certificates and private keys in a JKS or PKCS #12 key store.
|Install or update extension bundles. An extension bundle is a package of extensions that use the Server SDK to extend the functionality of the PingDirectory Server. Extension bundles are installed from a zip archive or file system directory. PingDirectory Server will be restarted if running to activate the extensions.
|Generate, compare, install, and replace server profiles.
|Access information about pending, running, and completed tasks scheduled in the Directory Server.
|Manage the topology registry.
|Migrate schema information from an existing LDAP server into a Ping Identity Directory Server instance.
|Update an instance of the Ping Identity Directory Server to match the configuration of an existing Sun Java System Directory Server 5.x, 6.x, or 7.x.
|Perform repeated modifications against an LDAP directory server.
|Move all entries in a specified subtree from one server to another.
|Perform add, delete, modify, and modify DN operations concurrently using multiple threads.
|Populate entries in one or more backends with attribute values generated by one or more composed attribute plugins.
|View information in data files captured by the Directory Server profiler.
|Initiate a task that causes a local DB backend to re-encode all or a specified subset of the entries that it contains. The tool does not alter the entries themselves but provides a useful mechanism for applying significant changes to the way that entries are stored in the backend (for example, to apply encoding changes if a feature like data encryption or uncached attributes or entries is enabled).
|Rebuild index data within a backend based on the Berkeley DB Java Edition. Note that this tool uses different approaches to rebuilding indexes based on whether it is running in online mode (as a task) rather than with the server offline. Running in offline mode will often provide significantly better performance and require significantly less database cleaning, particularly for indexes containing keys that match a large number of entries and have high index entry limit and exploded index entry threshold values. Also note that rebuilding an index with the server online will prevent the server from using that index while the rebuild is in progress, so some searches might behave differently while a rebuild is active than when it is not.
|Register a YubiKey OTP device with the Directory Server for a specified user so that the device can be used to authenticate that user in conjunction with the UNBOUNDID-YUBIKEY-OTP SASL mechanism. Alternately, it can be used to deregister one or more YubiKey OTP devices for a user so that they can no longer be used to authenticate that user.
|Reload HTTPS Connection Handler certificates.
|Safely remove a backup and optionally all of its dependent backups from the specified Directory Server backend.
|Remove a server from this server's topology.
|Replace the listener certificate for this Ping Identity Directory Server server instance.
|Restore a backup of a Directory Server backend.
|Revert this server package's most recent update.
|Review and/or indicate your acceptance of the license agreement defined in legal/LICENSE.txt.
|Trigger the rotation of one or more log files.
|Sanitize the contents of a server log file to remove potentially sensitive information while still attempting to retain enough information to make it useful for diagnosing problems or understanding load patterns. The sanitization process operates on fields that consist of name-value pairs. The field name is always preserved, but field values might be tokenized or redacted if they might include sensitive information. Supported log file types include the file-based access, error, sync, and resync logs, as well as the operation timing access log and the detailed HTTP operation log. Sanitize the audit log using the scramble-ldif tool.
|Schedule an exec task to run a specified command in the server. To
run an exec task, a number of conditions must be satisfied: the server's
global configuration must have been updated to include
'com.unboundid.directory.server.tasks.ExecTask' in the set of
allowed-task values, the requester must have the
exec-task privilege, and the command to execute must
be listed in the exec-command-whitelist.txt file in
the server's config directory. The absolute path (on
the server system) of the command to execute must be specified as the
first unnamed trailing argument to this program, and the arguments to
provide to that command (if any) should be specified as the remaining
trailing arguments. The server root is used as the command's working
directory, so any arguments that represent relative paths are interpreted
as relative to that directory.
|Perform repeated searches against an LDAP directory server and modify each entry returned.
|Search across log files to extract lines matching the provided patterns, like the grep command-line tool. The benefits of using this tool over grep are its ability to handle multiline log messages, extract log messages within a given time range, and the inclusion of rotated log files.
|Perform repeated searches against an LDAP directory server.
|View information about the current state of the Directory Server process.
|Request that the Directory Server assign appropriate ACI for configured delegated administrators of the Delegated Admin API.
|Perform the initial setup for a server instance.
|Start the Directory Server.
|Display basic server information.
|Stop or restart the server.
|List or update the set of subtree accessibility restrictions defined in the Directory Server.
|Calculate the sum of the sizes for a set of files.
|Generate a summary of one or more access logs to display a number of metrics about operations processed within the server.
|Apply one or more changes to entries or change records read from an LDIF file, writing the updating records to a new file. This tool can apply a variety of transformations, including scrambling attribute values, redacting attribute values, excluding attributes or entries, replacing existing attributes, adding new attributes, renaming attributes, and moving entries from one subtree to another.
|Uninstall Ping Identity Directory Server.
|Update the Directory Server to a newer version by downloading and unzipping the new server install package on the same host as the server you wish to update. Then, use the update tool from the new server package to update the older version of the server. Before upgrading a server, you should ensure that it is capable of starting without severe or fatal errors. During the update process, the server is stopped if running, then the update is performed, and a check is made to determine if the newly updated server starts without major errors. If it cannot start cleanly, the update will be backed out and the server returned to its prior state. See the revert-update tool for information on reverting an update.
|Validate a set of access control definitions contained in an LDAP server (including Sun/Oracle DSEE instances) or an LDIF file to determine whether they are acceptable for use in the Directory Server. Note that the output generated by this tool will be in LDIF format, but each entry in the output will have exactly one ACI, so entries that have more than one ACI will appear multiple times in the output with different ACI values.
|Validate file signatures. For best results, file signatures should be validated by the same instance used to generate the file. However, it might be possible to validate signatures generated on other instances in a replicated topology.
|Validate an LDAP schema read from one or more LDIF files.
|Validate the contents of an LDIF file against the server schema.
|Verify that indexes in a backend using the Berkeley DB Java Edition are consistent with the entry data contained in the database.
|Launch a window to watch an LDAP entry for changes. If the entry changes, the background of modified attributes will temporarily be red. Attributes can be modified as well. This tool is primarily intended to demonstrate replication or synchronization functionality.