.unboundid-ldapsdk.4.0.9.source-code.unboundid-ldapsdk-tools.properties Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of unboundid-ldapsdk Show documentation
Show all versions of unboundid-ldapsdk Show documentation
The UnboundID LDAP SDK for Java is a fast, comprehensive, and easy-to-use
Java API for communicating with LDAP directory servers and performing
related tasks like reading and writing LDIF, encoding and decoding data
using base64 and ASN.1 BER, and performing secure communication. This
package contains the Standard Edition of the LDAP SDK, which is a
complete, general-purpose library for communicating with LDAPv3 directory
servers.
# Copyright 2008-2018 Ping Identity Corporation
# All Rights Reserved.
# The fully-qualified name of the class to create.
class.name=com.unboundid.ldap.sdk.unboundidds.tools.ToolMessages
INFO_MANAGE_ACCT_TOOL_DESC=Retrieve or update information about the current \
state of a user account. Processing will be performed using the password \
policy state extended operation, and you must have the password-reset \
privilege to use this extended operation.
INFO_MANAGE_ACCT_ARG_GROUP_TARGET_USER_ARGS=Arguments for Identifying Target \
Users
INFO_MANAGE_ACCT_ARG_GROUP_PERFORMANCE=Arguments for Adjusting Performance
INFO_MANAGE_ACCT_ARG_DESC_TARGET_DN=The DN of the user entry on which to \
operate. This argument may be provided multiple times to specify multiple \
user DNs.
INFO_MANAGE_ACCT_ARG_DESC_DN_FILE=The path to a file containing the DNs of \
the user entries on which to operate. The DN file must contain one DN per \
line, and blank lines and lines starting with an octothorpe (#) will be \
ignored. This argument may be provided multiple times to use multiple DN \
files.
INFO_MANAGE_ACCT_ARG_DESC_TARGET_FILTER=An LDAP filter that may be used to \
identify the user entries on which to operate. The {0} argument may be \
used to specify the base DN for the search. This argument may be provided \
multiple times to specify multiple target filters.
INFO_MANAGE_ACCT_ARG_DESC_FILTER_INPUT_FILE=The path to a file containing a \
set of LDAP filters to use to identify the user entries on which to \
operate. The {0} argument may be used to specify the base DN for the \
searches. The filter file must contain one filter per line, and blank \
lines and lines starting with an octothorpe (#) will be ignored. This \
argument may be provided multiple times to use multiple filter files.
INFO_MANAGE_ACCT_ARG_DESC_TARGET_USER_ID=A string that identifies a user on \
which to operate. The tool will search for the user with a base DN \
specified by the {0} argument and a user ID attribute specified by the {1} \
argument. This argument may be provided multiple times to specify multiple \
target user IDs.
INFO_MANAGE_ACCT_ARG_DESC_USER_ID_INPUT_FILE=The path to a file containing a \
set of user ID values. The file must contain one user ID per line, and \
blank lines and lines starting with an octothorpe (#) will be ignored. The \
tool will search for the users with a base DN specified by the {0} argument \
and a user ID attribute specified by the {1} argument. This argument may \
be provided multiple times to use multiple user ID files.
INFO_MANAGE_ACCT_ARG_DESC_USER_ID_ATTR=The name or OID of the attribute used \
to identify users with IDs specified using the {0} and {1} arguments. If \
this argument is not provided, a default user ID attribute of {2} will be \
used.
INFO_MANAGE_ACCT_ARG_DESC_BASE_DN=The base DN to use when searching for user \
entries when using any of the {0}, {1}, {2}, or {3} arguments. If this \
argument is not provided, the default base DN will be the null DN.
INFO_MANAGE_ACCT_ARG_DESC_SIMPLE_PAGE_SIZE=Indicates that any searches \
performed to identify which users to target should make use of the simple \
paged results control to cause the entries to be returned in sets of no \
more than the specified number of entries. When processing searches that \
may return a large number of entries, setting a page size can help reduce \
the likelihood that the server will need to block while sending results \
to the client if matching entries are identified much more quickly than \
the client can process the desired {0} operations against those entries. \
Further, when performing searches that may return a large number of \
entries, and especially for unindexed searches, setting a page size can \
help the client more efficiently resume processing in the event that the \
connection used to process the search becomes unusable.
INFO_MANAGE_ACCT_ARG_DESC_NUM_THREADS=The number of concurrent threads to use \
when performing {0} operations against user entries. If this argument is \
not provided, a default value of one will be used.
INFO_MANAGE_ACCT_ARG_DESC_NUM_SEARCH_THREADS=The number of concurrent threads \
to use when searching for entries to target with {0} operations. This will \
only be used if arguments are provided that require the tool to perform \
searches to identify which entries to target (and will primarily be useful \
only in cases in which there will be multiple searches, as when reading \
filters or user IDs from a file). If this argument is not provided, a \
default value of one will be used.
INFO_MANAGE_ACCT_ARG_DESC_RATE_PER_SECOND=The maximum rate, in operations per \
second, at which to target user entries. If neither this nor the {0} \
argument is provided, then the tool will not perform any rate limiting.
INFO_MANAGE_ACCT_ARG_DESC_VARIABLE_RATE_DATA=The path to a file containing a \
variable rate definition that may be used to cause the tool to vary the \
amount of load it generates over time. If neither this nor the {0} \
argument is provided, then the tool will not perform any rate limiting.
INFO_MANAGE_ACCT_ARG_DESC_GENERATE_SAMPLE_RATE_FILE=The path to a file to \
create with a sample variable rate definition. This file will contain \
comments that describe the expected format for the file to use with the {0} \
argument.
INFO_MANAGE_ACCT_ARG_DESC_REJECT_FILE=The path to a file to write with a \
record of any unsuccessful attempts to retrieve or update account \
information for a user.
INFO_MANAGE_ACCT_ARG_DESC_APPEND_TO_REJECT_FILE=Indicates that the tool \
should append to the file specified by the {0} argument if it already \
exists. If this argument is not provided and the reject file already \
exists, it will be overwritten.
INFO_MANAGE_ACCT_ARG_DESC_SUPPRESS_EMPTY_RESULT_OPERATIONS=Indicates that the \
result information for each {0} operation processed should suppress \
information about password policy state operations included in the result \
that do not have any values. Operations presented without values generally \
indicated that the user's password policy is not configured for the \
associated functionality (e.g., if the password expiration time was \
requested but password expiration is not enabled in the user's password \
policy).
INFO_MANAGE_ACCT_SC_DESC_GET_ALL=Retrieve all available state information for \
a user.
INFO_MANAGE_ACCT_SC_GET_ALL_EXAMPLE=Retrieve all available state information \
for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_POLICY_DN=Retrieve the DN of the password policy \
that governs a user.
INFO_MANAGE_ACCT_SC_GET_POLICY_DN_EXAMPLE=Retrieve the DN of the password \
policy that governs user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_IS_USABLE=Determine whether a user account will \
be allowed to authenticate or be used as an alternate authorization identity.
INFO_MANAGE_ACCT_SC_GET_IS_USABLE_EXAMPLE=Determine whether user ''{0}'' will \
be permitted to authenticate or be used as an alternate authorization \
identity.
INFO_MANAGE_ACCT_SC_DESC_GET_USABILITY_NOTICES=Retrieve any password policy \
state account usability notice messages for a user. These messages may \
provide useful information about the state of the user account, but do not \
necessarily represent a current or imminent problem with the account.
INFO_MANAGE_ACCT_SC_GET_USABILITY_NOTICES_EXAMPLE=Retrieve any password \
policy state account usability notice messages for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_USABILITY_WARNINGS=Retrieve any password policy \
state account usability warning messages for a user. The messages may \
provide information about conditions that may leave a user account unusable \
in the near future unless corrective action is taken.
INFO_MANAGE_ACCT_SC_GET_USABILITY_WARNINGS_EXAMPLE=Retrieve any password \
policy state account usability warning messages for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_USABILITY_ERRORS=Retrieve any password policy \
state account usability error messages for a user. The messages may \
provide information about conditions that prevent a user account from \
authenticating, being used as an alternate authorization identity, or \
otherwise functioning normally.
INFO_MANAGE_ACCT_SC_GET_USABILITY_ERRORS_EXAMPLE=Retrieve any password \
policy state account usability error messages for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_PW_CHANGED_TIME=Retrieve the time that a user's \
password was last changed, whether via a self change or an administrative \
reset.
INFO_MANAGE_ACCT_SC_GET_PW_CHANGED_TIME_EXAMPLE=Retrieve the time that the \
password for user ''{0}'' was last changed.
INFO_MANAGE_ACCT_SC_DESC_SET_PW_CHANGED_TIME=Set the password changed time \
value for a user.
INFO_MANAGE_ACCT_SC_SET_PW_CHANGED_TIME_ARG_VALUE=The new value for the \
password changed time. It must be a timestamp formatted either in \
generalized time form or in the local time zone using one of the following \
formats: YYYYMMDDhhmmss.uuu, YYYYMMDDhhmmss, or YYYYMMDDhhmm. If this \
argument is not provided, the password changed time will be set to the \
current time.
INFO_MANAGE_ACCT_SC_SET_PW_CHANGED_TIME_EXAMPLE=Set the password changed time \
for user ''{0}'' to ''{1}''.
INFO_MANAGE_ACCT_SC_DESC_CLEAR_PW_CHANGED_TIME=Clear the password changed \
time value for a user. For password policy evaluations that require \
knowing when the user's password was last changed, the server will attempt \
to fall back to using the create timestamp, if available.
INFO_MANAGE_ACCT_SC_CLEAR_PW_CHANGED_TIME_EXAMPLE=Clear the password changed \
time for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_IS_DISABLED=Determine whether a user account has \
been disabled by an administrator and cannot authenticate or be used as an \
alternate authorization identity. This can also be accomplished with a \
standard LDAP search operation by determining whether the user entry has a \
ds-pwp-account-disabled operational attribute with a value of true.
INFO_MANAGE_ACCT_SC_GET_IS_DISABLED_EXAMPLE=Determine whether the account \
for user ''{0}'' has been disabled by an administrator.
INFO_MANAGE_ACCT_SC_DESC_SET_IS_DISABLED=Specify whether a user account is \
administratively disabled. A disabled account cannot authenticate or be \
used as an alternate authorization identity. This can also be accomplished \
with a standard LDAP modify operation by setting the value of the \
ds-pwp-account-disabled operational attribute in the user's entry with a \
value of either true or false (or by removing the attribute from the user's \
entry, which is equivalent to giving it a value of false).
INFO_MANAGE_ACCT_SC_SET_IS_DISABLED_ARG_VALUE=The new value for the flag \
indicating whether the user's account is disabled. The value must be \
either 'true' or 'false'.
INFO_MANAGE_ACCT_SC_SET_IS_DISABLED_EXAMPLE=Update user ''{0}'' to make the \
account administratively disabled.
INFO_MANAGE_ACCT_SC_DESC_CLEAR_IS_DISABLED=Clear the account disabled state \
information from a user entry, which is logically equivalent to using the \
{0} subcommand with an {1} value of false. This can also be accomplished \
with a standard LDAP modify operation by removing the \
ds-pwp-account-disabled operational attribute from the user's entry.
INFO_MANAGE_ACCT_SC_CLEAR_IS_DISABLED_EXAMPLE=Clear the account disabled \
state information for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_ACCT_ACT_TIME=Retrieve the account activation \
time for a user. If the activation time is in the future, the user cannot \
authenticate or be used as an alternate authorization identity. This can \
also be accomplished with a standard LDAP search operation by retrieving \
the ds-pwp-account-activation-time operational attribute from the user's \
entry.
INFO_MANAGE_ACCT_SC_GET_ACCT_ACT_TIME_EXAMPLE=Retrieve the account activation \
time for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_SET_ACCT_ACT_TIME=Set the account activation time \
for a user. If the activation time is in the future, the user cannot \
authenticate or be used as an alternate authorization identity. This can \
also be accomplished with a standard LDAP modify operation by setting the \
ds-pwp-account-activation-time attribute to have a generalized time \
representation of the desired activation time.
INFO_MANAGE_ACCT_SC_SET_ACCT_ACT_TIME_ARG_VALUE=The new value for the account \
activation time. It must be a timestamp formatted either in generalized \
time form or in the local time zone using one of the following formats: \
YYYYMMDDhhmmss.uuu, YYYYMMDDhhmmss, or YYYYMMDDhhmm. If this argument is \
not provided, the account activation time will be set to the current time.
INFO_MANAGE_ACCT_SC_SET_ACCT_ACT_TIME_EXAMPLE=Set the account activation time \
for user ''{0}'' to ''{1}''.
INFO_MANAGE_ACCT_SC_DESC_CLEAR_ACCT_ACT_TIME=Clear the account activation \
time for a user. If the account previously had an activation time in the \
future, this will make it immediately eligible for use. This can also be \
accomplished with a standard LDAP modify operation by removing the \
ds-pwp-account-activation-time attribute from the user's entry.
INFO_MANAGE_ACCT_SC_CLEAR_ACCT_ACT_TIME_EXAMPLE=Clear the account activation \
time for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_SECONDS_UNTIL_ACCT_ACT=Retrieve the length of \
time in seconds until a user's account is eligible for use.
INFO_MANAGE_ACCT_SC_GET_SECONDS_UNTIL_ACCT_ACT_EXAMPLE=Retrieve the length of \
time in seconds until user account ''{0}'' will be eligible for use.
INFO_MANAGE_ACCT_SC_DESC_GET_ACCT_NOT_YET_ACTIVE=Determine whether a user \
account has an activation time in the future and therefore cannot \
authenticate or be used as an alternate authorization identity.
INFO_MANAGE_ACCT_SC_GET_ACCT_NOT_YET_ACTIVE_EXAMPLE=Determine whether user \
''{0}'' has an account activation time in the future.
INFO_MANAGE_ACCT_SC_DESC_GET_ACCT_EXP_TIME=Retrieve the account expiration \
time for a user. If the expiration time is in the past, the user cannot \
authenticate or be used as an alternate authorization identity. This can \
also be accomplished with a standard LDAP search operation by retrieving \
the ds-pwp-account-expiration-time operational attribute from the user's \
entry.
INFO_MANAGE_ACCT_SC_GET_ACCT_EXP_TIME_EXAMPLE=Retrieve the account expiration \
time for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_SET_ACCT_EXP_TIME=Set the account expiration time \
for a user. If the expiration time is in the past, the user cannot \
authenticate or be used as an alternate authorization identity. This can \
also be accomplished with a standard LDAP modify operation by setting the \
ds-pwp-account-expiration-time attribute to have a generalized time \
representation of the desired expiration time.
INFO_MANAGE_ACCT_SC_SET_ACCT_EXP_TIME_ARG_VALUE=The new value for the account \
expiration time. It must be a timestamp formatted either in generalized \
time form or in the local time zone using one of the following formats: \
YYYYMMDDhhmmss.uuu, YYYYMMDDhhmmss, or YYYYMMDDhhmm. If this argument is \
not provided, the account expiration time will be set to the current time.
INFO_MANAGE_ACCT_SC_SET_ACCT_EXP_TIME_EXAMPLE=Set the account expiration time \
for user ''{0}'' to ''{1}''.
INFO_MANAGE_ACCT_SC_DESC_CLEAR_ACCT_EXP_TIME=Clear the account expiration \
time for a user. If the account previously had an expiration time in the \
past, this will make it immediately eligible for use. This can also be \
accomplished with a standard LDAP modify operation by removing the \
ds-pwp-account-expiration-time attribute from the user's entry.
INFO_MANAGE_ACCT_SC_CLEAR_ACCT_EXP_TIME_EXAMPLE=Clear the account expiration \
time for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_SECONDS_UNTIL_ACCT_EXP=Retrieve the length of \
time in seconds until a user's account expires.
INFO_MANAGE_ACCT_SC_GET_SECONDS_UNTIL_ACCT_EXP_EXAMPLE=Retrieve the length \
of time in seconds until user account ''{0}'' expires.
INFO_MANAGE_ACCT_SC_DESC_GET_ACCT_IS_EXPIRED=Determine whether a user account \
has an expiration time in the past and therefore cannot authenticate or be \
used as an alternate authorization identity.
INFO_MANAGE_ACCT_SC_GET_ACCT_IS_EXPIRED_EXAMPLE=Determine whether user \
''{0}'' has an account expiration time in the past.
INFO_MANAGE_ACCT_SC_DESC_GET_PW_EXP_WARNED_TIME=Retrieve the time that a user \
received the first warning about an upcoming password expiration. This \
will only be available if password expiration is enabled in the user's \
password policy.
INFO_MANAGE_ACCT_SC_GET_PW_EXP_WARNED_TIME_EXAMPLE=Retrieve the time that \
user ''{0}'' received the first warning about an upcoming password \
expiration.
INFO_MANAGE_ACCT_SC_DESC_SET_PW_EXP_WARNED_TIME=Specify the time that a user \
received the first warning about an upcoming password expiration. Note \
that this will not in itself trigger a password expiration warning nor \
cause any account status notification handlers to be invoked. This will \
have no effect if password expiration is not enabled in the user's password \
policy.
INFO_MANAGE_ACCT_SC_SET_PW_EXP_WARNED_TIME_ARG_VALUE=The new value for the \
password expiration warned time. It must be a timestamp formatted either \
in generalized time form or in the local time zone using one of the \
following formats: YYYYMMDDhhmmss.uuu, YYYYMMDDhhmmss, or YYYYMMDDhhmm. \
If this argument is not provided, the password expiration warned time will \
be set to the current time.
INFO_MANAGE_ACCT_SC_SET_PW_EXP_WARNED_TIME_EXAMPLE=Set the password \
expiration warned time for user ''{0}'' to ''{1}''.
INFO_MANAGE_ACCT_SC_DESC_CLEAR_PW_EXP_WARNED_TIME=Clear a record of any \
password expiration warning from a user's entry.
INFO_MANAGE_ACCT_SC_CLEAR_PW_EXP_WARNED_TIME_EXAMPLE=Clear the password \
expiration warned time for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_SECONDS_UNTIL_PW_EXP_WARNING=Retrieve the length \
of time in seconds until a user will be eligible to start receiving \
warnings about an upcoming password expiration. This will only be \
available if password expiration is enabled in the user's password policy.
INFO_MANAGE_ACCT_SC_GET_SECONDS_UNTIL_PW_EXP_WARNING_EXAMPLE=Retrieve the \
length of time in seconds until user ''{0}'' will be eligible to start \
receiving password expiration warnings.
INFO_MANAGE_ACCT_SC_DESC_GET_PW_EXP_TIME=Retrieves the time that a user's \
password will expire. This will only be available if password expiration \
is enabled in the user's password policy.
INFO_MANAGE_ACCT_SC_GET_PW_EXP_TIME_EXAMPLE=Retrieves the time that the \
password for user ''{0}'' will expire.
INFO_MANAGE_ACCT_SC_DESC_GET_SECONDS_UNTIL_PW_EXP=Retrieves the length of \
time in seconds until a user's password will expire. This will only be \
available if password expiration is available in the user's password policy.
INFO_MANAGE_ACCT_SC_GET_SECONDS_UNTIL_PW_EXP_EXAMPLE=Retrieves the length of \
time in seconds until the password for user ''{0}'' expires.
INFO_MANAGE_ACCT_SC_DESC_GET_PW_IS_EXPIRED=Determine whether a user account \
has an expired password and therefore cannot authenticate or be used as an \
alternate authorization identity.
INFO_MANAGE_ACCT_SC_GET_PW_IS_EXPIRED_EXAMPLE=Determine whether user ''{0}'' \
has an expired password.
INFO_MANAGE_ACCT_SC_DESC_GET_ACCT_FAILURE_LOCKED=Determines whether a user's \
account is locked as a result of too many failed authentication attempts. \
This will only be available if failure lockout is enabled in the user's \
password policy.
INFO_MANAGE_ACCT_SC_GET_ACCT_FAILURE_LOCKED_EXAMPLE=Determines whether the \
account for user ''{0}'' is locked as a result of too many failed \
authentication attempts.
INFO_MANAGE_ACCT_SC_DESC_SET_ACCT_FAILURE_LOCKED=Specifies whether a user's \
account should be locked as a result of too many failed authentication \
attempts. This will have no effect if failure lockout is not enabled in \
the user's password policy.
INFO_MANAGE_ACCT_SC_SET_ACCT_FAILURE_LOCKED_ARG_VALUE=Indicates whether the \
user's account should be locked as a result of too many failed \
authentication attempts. The value must be either 'true' (in which case \
the server will update the user's entry to include the necessary number of \
failed authentication attempts) or 'false' (in which case the server will \
clear information about any authentication failures from a user's entry).
INFO_MANAGE_ACCT_SC_SET_ACCT_FAILURE_LOCKED_EXAMPLE=Forces the account for \
user ''{0}'' to be locked as a result of too many failed authentication \
attempts.
INFO_MANAGE_ACCT_SC_DESC_GET_FAILURE_LOCKED_TIME=Retrieves the time that a \
user's account was locked as a result of too many failed authentication \
attempts. This will only be available if failure lockout is enabled in \
the user's password policy.
INFO_MANAGE_ACCT_SC_GET_FAILURE_LOCKED_TIME_EXAMPLE=Retrieves the time that \
the account for user ''{0}'' was locked as a result of too many failed \
authentication attempts.
INFO_MANAGE_ACCT_SC_DESC_GET_SECONDS_UNTIL_FAILURE_UNLOCK=Retrieves the \
length of time in seconds until a user's temporary failure lockout \
expires. This will only be available if failure lockout is enabled in the \
user's password policy.
INFO_MANAGE_ACCT_SC_GET_SECONDS_UNTIL_FAILURE_UNLOCK_EXAMPLE=Retrieves the \
length of time in seconds until the temporary failure lockout for user \
''{0}'' expires.
INFO_MANAGE_ACCT_SC_DESC_GET_AUTH_FAILURE_TIMES=Retrieves the timestamps for \
any failed authentication attempts for a user since the user's last \
successful authentication. This will only be available if failure lockout \
is enabled in the user's password policy.
INFO_MANAGE_ACCT_SC_GET_AUTH_FAILURE_TIMES_EXAMPLE=Retrieves the timestamps \
for any failed authentication attempts for user ''{0}'' since that user's \
last successful authentication.
INFO_MANAGE_ACCT_SC_DESC_ADD_AUTH_FAILURE_TIME=Adds one or more new values \
to the set of authentication failure times for a user. If the resulting \
set of authentication failure times has reached the configured lockout \
failure count, the user's account will be locked. This will have no effect \
if failure lockout is not enabled in the user's password policy.
INFO_MANAGE_ACCT_SC_ADD_AUTH_FAILURE_TIME_ARG_VALUE=A timestamp for an \
authentication failure time to add to the user's entry. It must be a \
timestamp formatted either in generalized time form or in the local time \
zone using one of the following formats: YYYYMMDDhhmmss.uuu, \
YYYYMMDDhhmmss, or YYYYMMDDhhmm. This argument may be provided multiple \
times to specify multiple authentication failure times. If this argument \
is not provided, the current time will be added to the set of \
authentication failure times.
INFO_MANAGE_ACCT_SC_ADD_AUTH_FAILURE_TIME_EXAMPLE=Adds the current time to \
the set of authentication failure times for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_SET_AUTH_FAILURE_TIMES=Sets the timestamps for \
failed authentication attempts for a user. If the number of authentication \
failure times provided is greater than or equal to the lockout failure \
count for the user's password policy, the user's account will be locked. \
This will have no effect if failure lockout is not enabled in the user's \
password policy.
INFO_MANAGE_ACCT_SC_SET_AUTH_FAILURE_TIMES_ARG_VALUE=A timestamp for an \
authentication failure time to set in the user's entry. It must be a \
timestamp formatted either in generalized time form or in the local time \
zone using one of the following formats: YYYYMMDDhhmmss.uuu, \
YYYYMMDDhhmmss, or YYYYMMDDhhmm. This argument may be provided multiple \
times to specify multiple authentication failure times. If this argument \
is not provided, the set of authentication failure times will be updated \
to include only the current time.
INFO_MANAGE_ACCT_SC_SET_AUTH_FAILURE_TIMES_EXAMPLE=Sets the authentication \
failure times for user ''{0}'' to include values of ''{1}'' and ''{2}''.
INFO_MANAGE_ACCT_SC_DESC_CLEAR_AUTH_FAILURE_TIMES=Clears the set of \
authentication failure times for a user. If the user's account had been \
locked be of too many failed authentication attempts, this will also clear \
that lockout.
INFO_MANAGE_ACCT_SC_CLEAR_AUTH_FAILURE_TIMES_EXAMPLE=Clears the \
authentication failure times for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_REMAINING_FAILURE_COUNT=Retrieves the number of \
additional failed authentication attempts that will be required to lock a \
user's account. This will only be available if failure lockout is enabled \
in the user's password policy.
INFO_MANAGE_ACCT_SC_GET_REMAINING_FAILURE_COUNT_EXAMPLE=Retrieves the \
remaining number of failed authentication attempts that will be required to \
lock the account for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_ACCT_IDLE_LOCKED=Determines whether a user's \
account is locked because it has been too long since the user last \
authenticated. This will only be available if idle lockout is enabled in \
the user's password policy.
INFO_MANAGE_ACCT_SC_GET_ACCT_IDLE_LOCKED_EXAMPLE=Determines whether the \
account for user ''{0}'' is locked because it has been too long since the \
user last authenticated.
INFO_MANAGE_ACCT_SC_DESC_GET_SECONDS_UNTIL_IDLE_LOCKOUT=Retrieves the length \
of time in seconds until the user's account will be locked because it has \
been too long since the user last authenticated. This will only be \
available if idle lockout is enabled in the user's password policy.
INFO_MANAGE_ACCT_SC_GET_SECONDS_UNTIL_IDLE_LOCKOUT_EXAMPLE=Retrieves the \
length of time until the account for user ''{0}'' will be locked because \
it has been too long since the user last authenticated.
INFO_MANAGE_ACCT_SC_DESC_GET_IDLE_LOCKOUT_TIME=Retrieves the time at which \
the user's account was locked because it had been too long since the user \
last authenticated, or the time it will be locked unless the user \
authenticates before that time. This will only be available if idle \
lockout is enabled in the user's password policy
INFO_MANAGE_ACCT_SC_GET_IDLE_LOCKOUT_TIME_EXAMPLE=Retrieves the time at which \
the account for user ''{0}'' was locked because it had been too long since \
the user had last authenticated.
INFO_MANAGE_ACCT_SC_DESC_GET_MUST_CHANGE_PW=Determines whether a user's \
password has been reset by an administrator and the user must choose a new \
password before they will be allowed to perform any other operations. This \
will only be available if force change on add or force change on reset is \
enabled in the user's password policy.
INFO_MANAGE_ACCT_SC_GET_MUST_CHANGE_PW_EXAMPLE=Determines whether the \
password for user ''{0}'' has been reset and must be changed before any \
other operations will be allowed.
INFO_MANAGE_ACCT_SC_DESC_SET_MUST_CHANGE_PW=Specifies whether a user's \
password has been reset by an administrator and the user must choose a new \
password before they will be allowed to perform any other operations. This \
will have no effect if neither force change on add nor force change on \
reset is enabled in the user's password policy.
INFO_MANAGE_ACCT_SC_SET_MUST_CHANGE_PW_ARG_VALUE=Indicates whether the user \
should be forced to choose a new password before being permitted to \
perform any other operations. The value must be either 'true' or 'false'.
INFO_MANAGE_ACCT_SC_SET_MUST_CHANGE_PW_EXAMPLE=Specifies that the password \
for user ''{0}'' has been reset by an administrator and must be changed \
before they will be allowed to perform any other operations.
INFO_MANAGE_ACCT_SC_DESC_CLEAR_MUST_CHANGE_PW=Clears the password reset state \
information from a user's account. If the account had previously been \
locked because the user failed to choose a new password in a timely manner \
after an administrative reset, that lockout will be lifted. This will have \
no effect if neither force change on add nor force change on reset is \
enabled in the user's password policy.
INFO_MANAGE_ACCT_SC_CLEAR_MUST_CHANGE_PW_EXAMPLE=Clears the password reset \
state information from the account for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_ACCT_IS_RESET_LOCKED=Determines whether the \
user's account is locked because the user failed to choose a new password \
in a timely manner after an administrative reset. This will only be \
available if either force change on add or force change on reset is enabled \
in the user's password policy, and if a maximum password reset age is \
defined in the user's password policy.
INFO_MANAGE_ACCT_SC_GET_ACCT_IS_RESET_LOCKED_EXAMPLE=Determines whether the \
account for user ''{0}'' is locked because the user failed to choose a new \
password in a timely manner after an administrative reset.
INFO_MANAGE_ACCT_SC_DESC_GET_SECONDS_UNTIL_RESET_LOCKOUT=Determines the \
length of time in seconds until the user's account will be locked unless \
they choose a new password after an administrative password reset. This \
will only be available if either force change on add or force change on \
reset is enabled in the user's password policy, and if a maximum password \
reset age is defined in the user's password policy.
INFO_MANAGE_ACCT_SC_GET_SECONDS_UNTIL_RESET_LOCKOUT_EXAMPLE=Determines the \
length of time in seconds until the account for user ''{0}'' will be \
locked unless they choose a new password.
INFO_MANAGE_ACCT_SC_DESC_GET_RESET_LOCKOUT_TIME=Retrieves the time that a \
user's account was or will be locked for failing to choose a new password \
in a timely manner after an administrative reset. This will only be \
available if either force change on add or force change on reset is enabled \
in the user's password policy, and if a maximum password reset age is \
defined in the user's password policy.
INFO_MANAGE_ACCT_SC_GET_RESET_LOCKOUT_TIME_EXAMPLE=Retrieves the time that \
the account for user ''{0}'' was or will be locked for failing to choose a \
new password in a timely manner after an administrative reset.
INFO_MANAGE_ACCT_SC_DESC_GET_LAST_LOGIN_TIME=Retrieves the time that a user \
last authenticated. This will only be available if last login time \
tracking is enabled in the user's password policy.
INFO_MANAGE_ACCT_SC_GET_LAST_LOGIN_TIME_EXAMPLE=Retrieves the time that user \
''{0}'' last authenticated.
INFO_MANAGE_ACCT_SC_DESC_SET_LAST_LOGIN_TIME=Specifies the time that a user \
last authenticated. This will have no effect if last login time tracking \
is not enabled in the user's password policy.
INFO_MANAGE_ACCT_SC_SET_LAST_LOGIN_TIME_ARG_VALUE=The timestamp to use for \
the last login time value. It must be a timestamp formatted either in \
generalized time form or in the local time zone using one of the following \
formats: YYYYMMDDhhmmss.uuu, YYYYMMDDhhmmss, or YYYYMMDDhhmm. If this \
argument is not provided, the last login time will be set to the current \
time.
INFO_MANAGE_ACCT_SC_SET_LAST_LOGIN_TIME_EXAMPLE=Sets the last login time for \
user ''{0}'' to ''{1}''.
INFO_MANAGE_ACCT_SC_DESC_CLEAR_LAST_LOGIN_TIME=Clears the last login time \
from a user's entry. This will have no effect if last login time tracking \
is not enabled in the user's password policy.
INFO_MANAGE_ACCT_SC_CLEAR_LAST_LOGIN_TIME_EXAMPLE=Clears the last login time \
for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_LAST_LOGIN_IP=Retrieves the IP address of the \
client from which a user last authenticated. This will only be available \
if last login IP address tracking is enabled in the user's password policy.
INFO_MANAGE_ACCT_SC_GET_LAST_LOGIN_IP_EXAMPLE=Retrieves the IP address of the \
client from which user ''{0}'' last authenticated.
INFO_MANAGE_ACCT_SC_DESC_SET_LAST_LOGIN_IP=Specifies the IP address of the \
client from which a user last authenticated. This will have no effect if \
last login IP address tracking is not enabled in the user's password policy.
INFO_MANAGE_ACCT_SC_SET_LAST_LOGIN_IP_ARG_VALUE=The last login IP address \
value to use. It may be an IPv4 or IPv6 address.
INFO_MANAGE_ACCT_SC_SET_LAST_LOGIN_IP_EXAMPLE=Sets the last login IP address \
for user ''{0}'' to ''{1}''.
INFO_MANAGE_ACCT_SC_DESC_CLEAR_LAST_LOGIN_IP=Clears the last login IP address \
from a user's entry. This will have no effect if last login IP address \
tracking is not enabled in the user's password policy.
INFO_MANAGE_ACCT_SC_CLEAR_LAST_LOGIN_IP_EXAMPLE=Clears the last login IP \
address for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_GRACE_LOGIN_TIMES=Retrieves the times that a \
user has authenticated with grace logins after their password had expired. \
This will only be available if both password expiration and grace login \
supports are configured in the user's password policy.
INFO_MANAGE_ACCT_SC_GET_GRACE_LOGIN_TIMES_EXAMPLE=Retrieves the grace login \
times for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_ADD_GRACE_LOGIN_TIME=Adds one or more new values to \
the set of grace login use times for a user. This will have no effect \
unless both password expiration and grace login support are configured in \
the user's password policy.
INFO_MANAGE_ACCT_SC_ADD_GRACE_LOGIN_TIME_ARG_VALUE=A timestamp for a grace \
login use time to add to the user's entry. It must be a timestamp \
formatted either in generalized time form or in the local time zone using \
one of the following formats: YYYYMMDDhhmmss.uuu, YYYYMMDDhhmmss, or \
YYYYMMDDhhmm. This argument may be provided multiple times to specify \
multiple grace login use times. If this argument is not provided, the \
current time will be used.
INFO_MANAGE_ACCT_SC_ADD_GRACE_LOGIN_TIME_EXAMPLE=Adds the current time to the \
set of grace login use times for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_SET_GRACE_LOGIN_TIMES=Replaces the set of grace \
login use times for a user. This will have no effect unless both password \
expiration and grace login support are configured in the user's password \
policy.
INFO_MANAGE_ACCT_SC_SET_GRACE_LOGIN_TIMES_ARG_VALUE=A timestamp for a grace \
login use time to set in the user's entry. It must be a timestamp \
formatted either in generalized time form or in the local time zone using \
one of the following formats: YYYYMMDDhhmmss.uuu, YYYYMMDDhhmmss, or \
YYYYMMDDhhmm. This argument may be provided multiple times to specify \
multiple grace login use times. If this argument is not provided, the \
set of grace login use times will be updated to contain only the current \
time.
INFO_MANAGE_ACCT_SC_SET_GRACE_LOGIN_TIMES_EXAMPLE=Sets the grace login use \
times for user ''{0}'' to be ''{1}'' and ''{2}''.
INFO_MANAGE_ACCT_SC_DESC_CLEAR_GRACE_LOGIN_TIMES=Clears the set of grace \
login use times for a user. This will have no effect unless both password \
expiration and grace login support are configured in the user's password \
policy.
INFO_MANAGE_ACCT_SC_CLEAR_GRACE_LOGIN_TIMES_EXAMPLE=Clears the set of grace \
login use times for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_REMAINING_GRACE_LOGIN_COUNT=Retrieves the number \
of additional grace logins that will be available to a user before they \
will be unable to authenticate with an expired password. This will only be \
available if both password expiration and grace login support are enabled \
in the user's password policy.
INFO_MANAGE_ACCT_SC_GET_REMAINING_GRACE_LOGIN_COUNT_EXAMPLE=Retrieves the \
remaining number of grace logins that for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_PW_CHANGED_BY_REQ_TIME=Retrieves the most recent \
required change time with which a user has complied. This will only be \
available if a required change time is configured in the user's password \
policy.
INFO_MANAGE_ACCT_SC_GET_PW_CHANGED_BY_REQ_TIME_EXAMPLE=Retrieves the most \
recent required change time with which user ''{0}'' has complied.
INFO_MANAGE_ACCT_SC_DESC_SET_PW_CHANGED_BY_REQ_TIME=Specifies the most recent \
required change time with which a user has complied. This will not have \
any effect unless a required change time is configured in the user's \
password policy.
INFO_MANAGE_ACCT_SC_SET_PW_CHANGED_BY_REQ_TIME_ARG_VALUE=The most recent \
required change time with which the user has complied. It must be a \
timestamp formatted either in generalized time form or in the local time \
zone using one of the following formats: YYYYMMDDhhmmss.uuu, \
YYYYMMDDhhmmss, or YYYYMMDDhhmm. If this argument is not provided, the \
most recent required change time will be used.
INFO_MANAGE_ACCT_SC_SET_PW_CHANGED_BY_REQ_TIME_EXAMPLE=Specifies that user \
''{0}'' has most recently complied with the most recent required change time.
INFO_MANAGE_ACCT_SC_DESC_CLEAR_PW_CHANGED_BY_REQ_TIME=Clears the record of \
the most recent required change time with which a user has complied. This \
will not have any effect unless a required change time is configured in the \
user's password policy.
INFO_MANAGE_ACCT_SC_CLEAR_PW_CHANGED_BY_REQ_TIME_EXAMPLE=Clears the record of \
the most recent required change time with which user ''{0}'' complied.
INFO_MANAGE_ACCT_SC_DESC_GET_SECS_UNTIL_REQ_CHANGE_TIME=Retrieves the length \
of time in seconds until the user account is locked for failure to comply \
with a required change time. This will only be available if a required \
change time is configured in the user's password policy.
INFO_MANAGE_ACCT_SC_GET_SECS_UNTIL_REQ_CHANGE_TIME_EXAMPLE=Retrieves the \
length of time in seconds until the account for user ''{0}'' is locked for \
failure to comply with a required change time.
INFO_MANAGE_ACCT_SC_DESC_GET_PW_HISTORY_COUNT=Retrieves the number of \
passwords in a user's password history. This will only be available if the \
password history is enabled in the user's password policy.
INFO_MANAGE_ACCT_SC_GET_PW_HISTORY_COUNT_EXAMPLE=Retrieves the number of \
passwords in the password history for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_CLEAR_PW_HISTORY=Clears the password history for a \
user. This will have no effect if the password history is not enabled in \
the user's password policy.
INFO_MANAGE_ACCT_SC_CLEAR_PW_HISTORY_EXAMPLE=Clears the password history for \
user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_HAS_RETIRED_PW=Determines whether a user has an \
active retired password.
INFO_MANAGE_ACCT_SC_GET_HAS_RETIRED_PW_EXAMPLE=Determines whether user \
''{0}'' has a retired password.
INFO_MANAGE_ACCT_SC_DESC_GET_PW_RETIRED_TIME=Retrieves the time that a user's \
former password was retired.
INFO_MANAGE_ACCT_SC_GET_PW_RETIRED_TIME_EXAMPLE=Retrieves the time the former \
password for user ''{0}'' was retired.
INFO_MANAGE_ACCT_SC_DESC_GET_RETIRED_PW_EXP_TIME=Retrieves the time that a \
user's retired password will expire.
INFO_MANAGE_ACCT_SC_GET_RETIRED_PW_EXP_TIME_EXAMPLE=Retrieves the time that \
the retired password for user ''{0}'' will expire.
INFO_MANAGE_ACCT_SC_DESC_PURGE_RETIRED_PW=Purges a retired password from a \
user's entry so that it may no longer be used to authenticate.
INFO_MANAGE_ACCT_SC_PURGE_RETIRED_PW_EXAMPLE=Purges a retired password for \
user ''{0}''.
ERR_MANAGE_ACCT_CANNOT_GENERATE_SAMPLE_RATE_FILE=An error occurred while \
attempting to write a sample variable rate definition to file ''{0}'': {1}
ERR_MANAGE_ACCT_CANNOT_CREATE_RATE_ADJUSTOR=An error occurred while \
attempting to initialize the variable-rate adjustor to alter the maximum \
load over time based on the definitions contained in file ''{0}'': {1}
ERR_MANAGE_ACCT_CANNOT_CREATE_CONNECTION_POOL=An error occurred while \
attempting to create a connection pool to perform {0} processing: {1}
ERR_MANAGE_ACCT_CANNOT_CREATE_REJECT_WRITER=An error occurred while \
attempting to create a reject writer to write information about failed \
operation attempts to file ''{0}'': {1}
ERR_MANAGE_ACCT_CANNOT_CREATE_PROCESSOR=An error occurred while attempting to \
initialize the password policy state operation processor: {0}
ERR_MANAGE_ACCT_CANNOT_BASE64_DECODE_DN=An error occurred while attempting to \
base64-decode the DN in line ''{0}'' read from file ''{1}'': {2}
ERR_MANAGE_ACCT_ERROR_READING_DN_FILE=An error occurred while attempting to \
read from DN file ''{0}'': {1}
ERR_MANAGE_ACCT_MALFORMED_FILTER_FROM_FILE=Filter file ''{0}'' contains \
line ''{1}'' that cannot be parsed as a valid search filter: {2}
ERR_MANAGE_ACCT_ERROR_READING_FILTER_FILE=An error occurred while attempting \
to read from filter file ''{0}'': {1}
ERR_MANAGE_ACCT_ERROR_READING_USER_ID_FILE=An error occurred while attempting \
to read from user ID file ''{0}'': {1}
NOTE_MANAGE_ACCT_UNSOLICITED_NOTIFICATION=NOTICE: Received an unsolicited \
notification on connection {0}: {1}
ERR_MANAGE_ACCT_PROCESSOR_NO_SUBCOMMAND=Unable to perform any {0} processing \
because no subcommand was selected.
ERR_MANAGE_ACCT_PROCESSOR_UNSUPPORTED_SUBCOMMAND=Support for the ''{0}'' \
subcommand is not currently implemented in the {1} tool.
ERR_MANAGE_ACCT_SEARCH_OP_ERROR_READING_PAGE_RESPONSE=An error occurred \
while attempting to retrieve a simple paged results response control from \
search result {0} for filter {1}: {2}
ERR_MANAGE_ACCT_SEARCH_OP_CANNOT_GET_CONNECTION=Unable to get an LDAP \
connection to use to process search request {0}: {1}
INFO_MANAGE_ACCT_SEARCH_OP_SUCCESSFUL_PAGE=Successfully retrieved a page of \
entries matching filter {0}. Entries returned: {1}.
INFO_MANAGE_ACCT_SEARCH_OP_SUCCESSFUL_FULL=Successfully completed the search \
matching filter {0}. Entries returned: {1}.
ERR_MANAGE_ACCT_SEARCH_OP_FAILED_NO_RETRY=An error occurred while attempting \
to search for entries matching filter {0}: {1} {2}. No retry attempt will \
be made for this search.
ERR_MANAGE_ACCT_SEARCH_OP_FAILED_SECOND_ATTEMPT=An error occurred while \
attempting to search for entries matching filter {0}: {1} {2}. This was \
the second attempt to process the search and no further retry attempts \
will be made.
ERR_MANAGE_ACCT_SEARCH_OP_EXCEPTION=An unexpected exception was raised while \
attempting to process search request {0}: {1}
WARN_MANAGE_ACCT_SEARCH_OP_REFERRAL=WARNING: Search result reference \
returned while searching for entries matching filter ''{0}'': {1}. This \
referral will not be followed, so entries only accessible via this referral \
will not be processed.
INFO_MANAGE_ACCT_SC_DESC_GET_AVAILABLE_SASL_MECHS=Retrieves a list of the \
SASL mechanisms that are available for a user. This will take into account \
the server configuration, the types of credentials the user has, and the \
authentication constraints defined for the user.
INFO_MANAGE_ACCT_SC_GET_AVAILABLE_SASL_MECHS_EXAMPLE=Retrieves a list of the \
SASL mechanisms that are available for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_AVAILABLE_OTP_MECHS=Retrieves a list of the \
one-time password delivery mechanisms that are available for a user. If \
the user's entry includes information about which OTP delivery mechanisms \
are preferred, then the values will be returned in order of most preferred \
to least preferred.
INFO_MANAGE_ACCT_SC_GET_AVAILABLE_OTP_MECHS_EXAMPLE=Retrieves a list of the \
one-time password delivery mechanisms that are available for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_HAS_TOTP_SHARED_SECRET=Determines whether a user \
has at least one TOTP shared secret that may be used in conjunction with \
the UNBOUNDID-TOTP SASL mechanism or the Verify TOTP extended operation.
INFO_MANAGE_ACCT_SC_GET_HAS_TOTP_SHARED_SECRET_EXAMPLE=Determines whether \
user ''{0}'' has at least one TOTP shared secret.
INFO_MANAGE_ACCT_SC_DESC_ADD_TOTP_SHARED_SECRET=Adds a value to the set of \
TOTP shared secrets for a user.
INFO_MANAGE_ACCT_SC_ADD_TOTP_SHARED_SECRET_EXAMPLE=Adds value ''{0}'' to the \
set of TOTP shared secrets for user ''{1}''.
INFO_MANAGE_ACCT_SC_ADD_TOTP_SHARED_SECRET_ARG_VALUE=The TOTP shared secret \
to register for a user. This argument must be provided at least once, but \
may be provided multiple times to specify multiple TOTP shared secrets to \
register.
INFO_MANAGE_ACCT_SC_DESC_REMOVE_TOTP_SHARED_SECRET=Removes a value from the \
set of TOTP shared secrets for a user.
INFO_MANAGE_ACCT_SC_REMOVE_TOTP_SHARED_SECRET_EXAMPLE=Removes value ''{0}'' \
from the set of TOTP shared secrets for user ''{1}''.
INFO_MANAGE_ACCT_SC_REMOVE_TOTP_SHARED_SECRET_ARG_VALUE=The TOTP shared \
secret to deregister for a user. This argument must be provided at least \
once, but may be provided multiple times to specify multiple TOTP shared \
secrets to deregister.
INFO_MANAGE_ACCT_SC_DESC_SET_TOTP_SHARED_SECRETS=Replaces the set of TOTP \
shared secrets registered for a user.
INFO_MANAGE_ACCT_SC_SET_TOTP_SHARED_SECRETS_EXAMPLE=Replaces the set of TOTP \
shared secrets for user ''{0}'' with a single value of ''{1}''.
INFO_MANAGE_ACCT_SC_SET_TOTP_SHARED_SECRETS_ARG_VALUE=The TOTP shared secret \
to register for a user. This argument must be provided at least once, but \
may be provided multiple times to specify multiple TOTP shared secrets to \
register.
INFO_MANAGE_ACCT_SC_DESC_CLEAR_TOTP_SHARED_SECRETS=Clears the set of TOTP \
shared secrets registered for a user.
INFO_MANAGE_ACCT_SC_CLEAR_TOTP_SHARED_SECRETS_EXAMPLE=Clears the set of TOTP \
shared secrets registered for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_HAS_YUBIKEY_ID=Determines whether a user has at \
least one registered YubiKey OTP device public ID.
INFO_MANAGE_ACCT_SC_GET_HAS_YUBIKEY_ID_EXAMPLE=Determines whether user \
''{0}'' has at least one registered YubiKey OTP device public ID.
INFO_MANAGE_ACCT_SC_DESC_GET_YUBIKEY_IDS=Retrieves a list of the public IDs \
of the YubiKey OTP devices registered for a user.
INFO_MANAGE_ACCT_SC_GET_YUBIKEY_IDS_EXAMPLE=Retrieves a list of the public \
IDs of the YubiKey OTP devices registered for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_ADD_YUBIKEY_ID=Adds a value to the set of registered \
YubiKey OTP public IDs for a user.
INFO_MANAGE_ACCT_SC_ADD_YUBIKEY_ID_EXAMPLE=Adds value ''{0}'' to the set of \
registered YubiKey OTP public IDs for user ''{1}''.
INFO_MANAGE_ACCT_SC_ADD_YUBIKEY_ID_ARG_VALUE=The public ID for a YubiKey OTP \
device to register for a user. This argument must be provided at least \
once, but may be provided multiple times to specify multiple public IDs to \
register.
INFO_MANAGE_ACCT_SC_DESC_REMOVE_YUBIKEY_ID=Removes a value from the set of \
registered YubiKey OTP public IDs for a user.
INFO_MANAGE_ACCT_SC_REMOVE_YUBIKEY_ID_EXAMPLE=Removes value ''{0}'' from the \
set of registered YubiKey OTP public IDs for user ''{1}''.
INFO_MANAGE_ACCT_SC_REMOVE_YUBIKEY_ID_ARG_VALUE=The public ID for a YubiKey \
OTP device to deregister for a user. This argument must be provided at \
least once, but may be provided multiple times to specify multiple public \
IDs to deregister.
INFO_MANAGE_ACCT_SC_DESC_SET_YUBIKEY_IDS=Replaces the list of the public \
IDs of the YubiKey OTP devices registered for a user.
INFO_MANAGE_ACCT_SC_SET_YUBIKEY_IDS_EXAMPLE=Replaces the list of the public \
IDs of the YubiKey OTP devices registered for user ''{0}'' with a single \
public ID of ''{1}''.
INFO_MANAGE_ACCT_SC_SET_YUBIKEY_IDS_ARG_VALUE=The public ID for a YubiKey OTP \
device to register for a user. This argument must be provided at least \
once, but may be provided multiple times to specify multiple public IDs to \
register.
INFO_MANAGE_ACCT_SC_DESC_CLEAR_YUBIKEY_IDS=Clears the list of the public IDs \
of the YubiKey OTP devices registered for a user.
INFO_MANAGE_ACCT_SC_CLEAR_YUBIKEY_IDS_EXAMPLE=Clears the list of the public \
IDs of the YubiKey OTP devices registered for user ''{0}''.
INFO_MANAGE_ACCT_SC_DESC_GET_HAS_STATIC_PW=Determines whether a user has one \
static password.
INFO_MANAGE_ACCT_SC_GET_HAS_STATIC_PW_EXAMPLE=Determines whether user \
''{0}'' has a static password.
INFO_GEN_TOTP_SECRET_TOOL_DESC=Generate a shared secret that may be used to \
generate time-based one-time password (TOTP) authentication codes for use \
in authenticating with the UNBOUNDID-TOTP SASL mechanism, or in conjunction \
with the validate TOTP password extended operation.
INFO_GEN_TOTP_SECRET_PLACEHOLDER_AUTH_ID={authID}
INFO_GEN_TOTP_SECRET_DESCRIPTION_AUTH_ID=An authentication ID that identifies \
the user for whom the TOTP shared secret should be generated. This must \
be provided, and it should either be in the form "dn:" followed by the DN \
of the target user's entry, or in the form "u:" followed by the username \
for the target user.
INFO_GEN_TOTP_SECRET_PLACEHOLDER_USER_PW={password}
INFO_GEN_TOTP_SECRET_DESCRIPTION_USER_PW=The static password for the user \
targeted by the {0} argument.
INFO_GEN_TOTP_SECRET_DESCRIPTION_USER_PW_FILE=The path to a file containing \
the static password for the user targeted by the {0} argument.
INFO_GEN_TOTP_SECRET_DESCRIPTION_PROMPT_FOR_USER_PW=Indicates that the tool \
should interactively prompt for the static password for the user targeted \
by the {0} argument.
INFO_GEN_TOTP_SECRET_PLACEHOLDER_SECRET={totpSharedSecret}
INFO_GEN_TOTP_SECRET_DESCRIPTION_REVOKE=Indicates that the server should \
revoke the provided TOTP shared secret rather than generating a new secret \
for the specified user.
INFO_GEN_TOTP_SECRET_DESCRIPTION_REVOKE_ALL=Indicates that the server \
should revoke all existing TOTP shared secrets for the specified user \
rather than generating a new secret.
ERR_GEN_TOTP_SECRET_CANNOT_CONNECT=An error occurred while attempting to \
establish a connection to use to communicate with the server: {0}
ERR_GEN_TOTP_SECRET_CANNOT_READ_PW_FROM_FILE=An error occurred while \
attempting to read the static password from file ''{0}'': {1}
INFO_GEN_TOTP_SECRET_ENTER_PW=Enter the static password for user ''{0}'':
ERR_GEN_TOTP_SECRET_CANNOT_READ_PW_FROM_STDIN=An error occurred while \
attempting to read the static password from standard input: {0}
INFO_GEN_TOTP_SECRET_REVOKE_SUCCESS=Successfully revoked TOTP shared secret \
''{0}''.
ERR_GEN_TOTP_SECRET_REVOKE_FAILURE=Unable to revoke TOTP shared secret {0}.
INFO_GEN_TOTP_SECRET_REVOKE_ALL_SUCCESS=Successfully revoked all TOTP shared \
secrets.
ERR_GEN_TOTP_SECRET_REVOKE_ALL_FAILURE=Unable to revoke all TOTP shared \
secrets.
INFO_GEN_TOTP_SECRET_GEN_SUCCESS=Successfully generated TOTP shared secret \
''{0}''.
ERR_GEN_TOTP_SECRET_GEN_FAILURE=Unable to generate a TOTP shared secret.
ERR_GEN_TOTP_SECRET_RESULT_CODE=Result code: {0}
ERR_GEN_TOTP_SECRET_DIAGNOSTIC_MESSAGE=Diagnostic Message: {0}
ERR_GEN_TOTP_SECRET_MATCHED_DN=Matched DN: {0}
ERR_GEN_TOTP_SECRET_REFERRAL_URL=Referral URL: {0}
INFO_GEN_TOTP_SECRET_GEN_EXAMPLE=Generate a TOTP secret for the user with \
username 'john.doe' and a password entered at an interactive prompt.
INFO_GEN_TOTP_SECRET_REVOKE_ALL_EXAMPLE=Revoke all TOTP shared secrets for \
for the user with username 'john.doe' whose password is contained in file \
'password.txt'.
INFO_PLACEHOLDER_ATTR={attr}
INFO_PLACEHOLDER_AUTHZID={authzID}
INFO_PLACEHOLDER_FIELD_NAME={fieldName}
INFO_PLACEHOLDER_FILTER={filter}
INFO_PLACEHOLDER_LEVEL={level}
INFO_PLACEHOLDER_NUM={num}
INFO_PLACEHOLDER_PATH={path}
INFO_PLACEHOLDER_PURPOSE={purpose}
INFO_PLACEHOLDER_TIMEOUT={timeout}
INFO_RESULT_UTILS_RESULT_CODE=Result Code: {0}
INFO_RESULT_UTILS_SUCCESS_WITH_TXN=NOTE: No changes will actually be applied \
to the server until the transaction is committed.
INFO_RESULT_UTILS_DIAGNOSTIC_MESSAGE: Diagnostic Message: {0}
INFO_RESULT_UTILS_MATCHED_DN=Matched DN: {0}
INFO_RESULT_UTILS_REFERRAL_URL=Referral URL: {0}
INFO_RESULT_UTILS_NUM_SEARCH_ENTRIES=Number of Entries Returned: {0,number,0}
INFO_RESULT_UTILS_NUM_SEARCH_REFERENCES=Number of References Returned: \
{0,number,0}
INFO_RESULT_UTILS_START_TXN_RESULT_TXN_ID=Start Transaction Extended Result \
Transaction ID: {0}
INFO_RESULT_UTILS_END_TXN_RESULT_FAILED_MSG_ID=End Transaction Extended \
Result Failed Operation Message ID: {0}
INFO_RESULT_UTILS_END_TXN_RESULT_OP_CONTROL=End Transaction Extended Result \
Response Control for Message ID {0}:
INFO_RESULT_UTILS_MULTI_UPDATE_CHANGES_APPLIED=Multi-Update Changes Applied: \
{0}
INFO_RESULT_UTILS_MULTI_UPDATE_RESULT_HEADER=Multi-Update {0} Operation Result:
INFO_RESULT_UTILS_PASSWORD_MODIFY_RESULT_GENERATED_PW=Password Modify \
Extended Result Generated Password: {0}
INFO_RESULT_UTILS_NOTICE_OF_DISCONNECTION_HEADER=Notice of Disconnection \
Unsolicited Notification
INFO_RESULT_UTILS_ABORTED_TXN_HEADER=Aborted Transaction Unsolicited \
Notification
INFO_RESULT_UTILS_TXN_ID_HEADER=Transaction ID: {0}
INFO_RESULT_UTILS_UNSOLICITED_NOTIFICATION_HEADER=Unsolicited Notification
INFO_RESULT_UTILS_RESPONSE_EXTOP_OID=Extended Result OID: {0}
INFO_RESULT_UTILS_RESPONSE_EXTOP_RAW_VALUE_HEADER=Extended Result Raw Value:
INFO_RESULT_UTILS_GENERIC_RESPONSE_CONTROL_HEADER=Response Control:
INFO_RESULT_UTILS_RESPONSE_CONTROL_OID=OID: {0}
INFO_RESULT_UTILS_RESPONSE_CONTROL_IS_CRITICAL=Is Critical: {0}
INFO_RESULT_UTILS_RESPONSE_CONTROL_RAW_VALUE_HEADER=Raw Value:
INFO_RESULT_UTILS_AUTHZ_ID_RESPONSE_HEADER=Authorization Identity Response \
Control:
INFO_RESULT_UTILS_AUTHZ_ID_RESPONSE_ID=Authorization ID: {0}
INFO_RESULT_UTILS_CONTENT_SYNC_DONE_RESPONSE_HEADER=Content Synchronization \
Done Response Control:
INFO_RESULT_UTILS_CONTENT_SYNC_DONE_REFRESH_DELETES:Refresh Deletes: {0}
INFO_RESULT_UTILS_CONTENT_SYNC_DONE_COOKIE_HEADER:Cookie Data:
INFO_RESULT_UTILS_CONTENT_SYNC_STATE_RESPONSE_HEADER=Content Synchronization \
State Response Control:
INFO_RESULT_UTILS_CONTENT_SYNC_STATE_ENTRY_UUID:Entry UUID: {0}
INFO_RESULT_UTILS_CONTENT_SYNC_STATE_NAME=Synchronization State: {0}
INFO_RESULT_UTILS_CONTENT_SYNC_STATE_COOKIE_HEADER:Cookie Data:
INFO_RESULT_UTILS_ECN_HEADER=Entry Change Notification Control:
INFO_RESULT_UTILS_ECN_CHANGE_TYPE=Change Type: {0}
INFO_RESULT_UTILS_ECN_CHANGE_NUMBER=Change Number: {0,number,0}
INFO_RESULT_UTILS_ECN_PREVIOUS_DN=Previous DN: {0}
INFO_RESULT_UTILS_PASSWORD_EXPIRED_HEADER=Password Expired Response Control:
INFO_RESULT_UTILS_PASSWORD_EXPIRING_HEADER=Password Expiring Response Control:
INFO_RESULT_UTILS_PASSWORD_EXPIRING_SECONDS_UNTIL_EXPIRATION=Seconds Until \
Expiration: {0,number,0}
INFO_RESULT_UTILS_POST_READ_HEADER=Post-Read Response Control:
INFO_RESULT_UTILS_POST_READ_ENTRY_HEADER=Post-Read Entry:
INFO_RESULT_UTILS_PRE_READ_HEADER=Pre-Read Response Control:
INFO_RESULT_UTILS_PRE_READ_ENTRY_HEADER=Pre-Read Entry:
INFO_RESULT_UTILS_SORT_HEADER=Server-Side Sort Response Control:
INFO_RESULT_UTILS_SORT_RESULT_CODE=Result Code: {0}
INFO_RESULT_UTILS_SORT_ATTRIBUTE_NAME=Attribute Name: {0}
INFO_RESULT_UTILS_PAGED_RESULTS_HEADER=Simple Paged Results Response Control:
INFO_RESULT_UTILS_PAGED_RESULTS_COUNT=Estimated Total Result Set Size: \
{0,number,0}
INFO_RESULT_UTILS_PAGED_RESULTS_COOKIE_HEADER=Cookie Data:
INFO_RESULT_UTILS_VLV_HEADER=Virtual List View Response Control:
INFO_RESULT_UTILS_VLV_RESULT_CODE=Result Code: {0}
INFO_RESULT_UTILS_VLV_CONTENT_COUNT=Estimated Content Count: {0,number,0}
INFO_RESULT_UTILS_VLV_TARGET_POSITION=Target Position: {0,number,0}
INFO_RESULT_UTILS_VLV_CONTEXT_ID_HEADER=Context ID:
INFO_RESULT_UTILS_ACCOUNT_USABLE_HEADER=Account Usable Response Control:
INFO_RESULT_UTILS_ACCOUNT_USABLE_IS_USABLE:Account Is Usable: {0}
INFO_RESULT_UTILS_ACCOUNT_USABLE_UNUSABLE_REASONS_HEADER:Unusable Reasons:
INFO_RESULT_UTILS_ACCOUNT_USABLE_PW_EXPIRED=Password Is Expired: {0}
INFO_RESULT_UTILS_ACCOUNT_USABLE_MUST_CHANGE_PW=Must Change Password: {0}
INFO_RESULT_UTILS_ACCOUNT_USABLE_IS_INACTIVE=Account Is Inactive: {0}
INFO_RESULT_UTILS_ACCOUNT_USABLE_REMAINING_GRACE=Remaining Grace Logins: \
{0,number,0}
INFO_RESULT_UTILS_ACCOUNT_USABLE_SECONDS_UNTIL_EXPIRATION=Seconds Until \
Password Expiration: {0,number,0}
INFO_RESULT_UTILS_ACCOUNT_USABLE_SECONDS_UNTIL_UNLOCK=Seconds Until Account \
Unlock: {0,number,0}
INFO_RESULT_UTILS_ASSURED_REPL_HEADER=Assured Replication Response Control:
INFO_RESULT_UTILS_ASSURED_REPL_CSN=Change Sequence Number: {0}
INFO_RESULT_UTILS_ASSURED_REPL_LOCAL_LEVEL=Local Assurance Level: {0}
INFO_RESULT_UTILS_ASSURED_REPL_LOCAL_SATISFIED=Local Assurance Satisfied: {0}
INFO_RESULT_UTILS_ASSURED_REPL_LOCAL_MESSAGE=Local Assurance Message: {0}
INFO_RESULT_UTILS_ASSURED_REPL_REMOTE_LEVEL=Remote Assurance Level: {0}
INFO_RESULT_UTILS_ASSURED_REPL_REMOTE_SATISFIED=Remote Assurance Satisfied: \
{0}
INFO_RESULT_UTILS_ASSURED_REPL_REMOTE_MESSAGE=Remote Assurance Message: {0}
INFO_RESULT_UTILS_ASSURED_REPL_SERVER_RESULT_HEADER=Server Result:
INFO_RESULT_UTILS_ASSURED_REPL_SERVER_RESULT_CODE=Server Result Code: {0}
INFO_RESULT_UTILS_ASSURED_REPL_SERVER_RESULT_REPL_SERVER_ID=Replication \
Server ID: {0,number,0}
INFO_RESULT_UTILS_ASSURED_REPL_SERVER_RESULT_REPL_ID=Replica ID: {0,number,0}
INFO_RESULT_UTILS_GET_AUTHZ_ENTRY_HEADER=Get Authorization Entry Response \
Control:
INFO_RESULT_UTILS_GET_AUTHZ_ENTRY_IS_AUTHENTICATED=Is Authenticated: {0}
INFO_RESULT_UTILS_GET_AUTHZ_ENTRY_IDS_MATCH=Authentication and Authorization \
Identities Match: {0}
INFO_RESULT_UTILS_GET_AUTHZ_ENTRY_AUTHN_ID=Authentication Identity ID: {0}
INFO_RESULT_UTILS_GET_AUTHZ_ENTRY_AUTHN_ENTRY_HEADER=Authentication Identity \
Entry:
INFO_RESULT_UTILS_GET_AUTHZ_ENTRY_AUTHZ_ID=Authorization Identity ID: {0}
INFO_RESULT_UTILS_GET_AUTHZ_ENTRY_AUTHZ_ENTRY_HEADER=Authorization Identity \
Entry:
INFO_RESULT_UTILS_GET_BACKEND_SET_ID_HEADER=Get Backend Set ID Response \
Control:
INFO_RESULT_UTILS_GET_BACKEND_SET_ID_EB_RP_ID=Entry-Balancing Request \
Processor ID: {0}
INFO_RESULT_UTILS_GET_BACKEND_SET_ID=Backend Set ID: {0}
INFO_RESULT_UTILS_GET_PW_STATE_ISSUES_HEADER=Get Password Policy State Issues \
Response Control:
INFO_RESULT_UTILS_GET_PW_STATE_ISSUES_FAILURE_REASON_HEADER=Authentication \
Failure Reason:
INFO_RESULT_UTILS_GET_PW_STATE_ISSUES_FAILURE_TYPE=Failure Type: {0}
INFO_RESULT_UTILS_GET_PW_STATE_ISSUES_FAILURE_MESSAGE=Failure Message: {0}
INFO_RESULT_UTILS_GET_PW_STATE_ISSUES_ERROR_HEADER=Account Usability Error:
INFO_RESULT_UTILS_GET_PW_STATE_ISSUES_ERROR_NAME=Error Name: {0}
INFO_RESULT_UTILS_GET_PW_STATE_ISSUES_ERROR_MESSAGE=Error Message: {0}
INFO_RESULT_UTILS_GET_PW_STATE_ISSUES_WARNING_HEADER=Account Usability Warning:
INFO_RESULT_UTILS_GET_PW_STATE_ISSUES_WARNING_NAME=Warning Name: {0}
INFO_RESULT_UTILS_GET_PW_STATE_ISSUES_WARNING_MESSAGE=Warning Message: {0}
INFO_RESULT_UTILS_GET_PW_STATE_ISSUES_NOTICE_HEADER=Account Usability Notice:
INFO_RESULT_UTILS_GET_PW_STATE_ISSUES_NOTICE_NAME=Notice Name: {0}
INFO_RESULT_UTILS_GET_PW_STATE_ISSUES_NOTICE_MESSAGE=Notice Message: {0}
INFO_RESULT_UTILS_GET_SERVER_ID_HEADER=Get Server ID Response Control:
INFO_RESULT_UTILS_GET_SERVER_ID=Server ID: {0}
INFO_RESULT_UTILS_GET_USER_RLIM_HEADER=Get User Resource Limits Response \
Control:
INFO_RESULT_UTILS_GET_USER_RLIM_VALUE_UNLIMITED=Unlimited
INFO_RESULT_UTILS_GET_USER_RLIM_UNIT_SECONDS=seconds
INFO_RESULT_UTILS_GET_USER_RLIM_SIZE_LIMIT=Size Limit: {0}
INFO_RESULT_UTILS_GET_USER_RLIM_TIME_LIMIT=Time Limit: {0}
INFO_RESULT_UTILS_GET_USER_RLIM_IDLE_TIME_LIMIT=Idle Time Limit: {0}
INFO_RESULT_UTILS_GET_USER_RLIM_LOOKTHROUGH_LIMIT=Lookthrough Limit: {0}
INFO_RESULT_UTILS_GET_USER_RLIM_EQUIVALENT_AUTHZ_USER_DN=Equivalent \
Authorization User DN: {0}
INFO_RESULT_UTILS_GET_USER_RLIM_CCP_NAME=Client Connection Policy Name: {0}
INFO_RESULT_UTILS_GET_USER_RLIM_GROUP_DNS_HEADER=Group DNs:
INFO_RESULT_UTILS_GET_USER_RLIM_PRIVILEGES_HEADER=Privileges:
INFO_RESULT_UTILS_GET_USER_RLIM_OTHER_ATTRIBUTES_HEADER=Other Attributes:
INFO_RESULT_UTILS_INTERMEDIATE_CLIENT_HEADER=Intermediate Client Response \
Control:
INFO_RESULT_UTILS_INTERMEDIATE_CLIENT_UPSTREAM_ADDRESS=Upstream Server \
Address: {0}
INFO_RESULT_UTILS_INTERMEDIATE_CLIENT_UPSTREAM_SECURE=Upstream Server \
Secure: {0}
INFO_RESULT_UTILS_INTERMEDIATE_CLIENT_SERVER_NAME=Server Name: {0}
INFO_RESULT_UTILS_INTERMEDIATE_CLIENT_SESSION_ID=Server Session ID: {0}
INFO_RESULT_UTILS_INTERMEDIATE_CLIENT_RESPONSE_ID=Server Response ID: {0}
INFO_RESULT_UTILS_INTERMEDIATE_CLIENT_UPSTREAM_RESPONSE_HEADER=Upstream \
Response:
INFO_RESULT_UTILS_JOIN_HEADER=Join Result Control:
INFO_RESULT_UTILS_JOIN_RESULT_CODE=Join Result Code: {0}
INFO_RESULT_UTILS_JOIN_DIAGNOSTIC_MESSAGE=Join Diagnostic Message: {0}
INFO_RESULT_UTILS_JOIN_MATCHED_DN=Join Matched DN: {0}
INFO_RESULT_UTILS_JOIN_REFERRAL_URL=Join Referral URL: {0}
INFO_RESULT_UTILS_JOINED_WITH_ENTRY_HEADER=Joined With Entry:
INFO_RESULT_UTILS_MATCHING_ENTRY_COUNT_HEADER=Matching Entry Count Response \
Control:
INFO_RESULT_UTILS_MATCHING_ENTRY_COUNT_TYPE_EXAMINED=Count Type: Examined
INFO_RESULT_UTILS_MATCHING_ENTRY_COUNT_TYPE_UNEXAMINED=Count Type: Unexamined
INFO_RESULT_UTILS_MATCHING_ENTRY_COUNT_TYPE_UPPER_BOUND=Count Type: Upper \
Bound
INFO_RESULT_UTILS_MATCHING_ENTRY_COUNT_TYPE_UNKNOWN=Count Type: Unknown
INFO_RESULT_UTILS_MATCHING_ENTRY_COUNT_VALUE=Count Value: {0,number,0}
INFO_RESULT_UTILS_MATCHING_ENTRY_COUNT_INDEXED=Search Is Indexed: {0}
INFO_RESULT_UTILS_MATCHING_ENTRY_COUNT_DEBUG_HEADER=Debug Info:
INFO_RESULT_UTILS_PW_POLICY_HEADER=Password Policy Response Control:
INFO_RESULT_UTILS_PW_POLICY_ERROR_TYPE=Error Type: {0}
INFO_RESULT_UTILS_PW_POLICY_ERROR_TYPE_NONE=Error Type: None
INFO_RESULT_UTILS_PW_POLICY_WARNING_TYPE=Warning Type: {0}
INFO_RESULT_UTILS_PW_POLICY_WARNING_TYPE_NONE=Warning Type: None
INFO_RESULT_UTILS_PW_POLICY_WARNING_VALUE=Warning Value: {0,number,0}
INFO_RESULT_UTILS_PW_VALIDATION_DETAILS_HEADER=Password Validation Details \
Response Control:
INFO_RESULT_UTILS_PW_VALIDATION_DETAILS_RESULT_TYPE_RESULT=Result Type: \
Validation Result
INFO_RESULT_UTILS_PW_VALIDATION_DETAILS_RESULT_TYPE_NO_PW=Result Type: No \
Password Provided
INFO_RESULT_UTILS_PW_VALIDATION_DETAILS_RESULT_TYPE_MULTIPLE_PW=Result \
Type: Multiple Passwords Provided
INFO_RESULT_UTILS_PW_VALIDATION_DETAILS_RESULT_TYPE_NO_VALIDATION=Result \
Type: No Validation Attempted
INFO_RESULT_UTILS_PW_VALIDATION_DETAILS_RESULT_TYPE_DEFAULT=Result Type: {0}
INFO_RESULT_UTILS_PW_VALIDATION_DETAILS_MISSING_CURRENT=Missing Current \
Password: {0}
INFO_RESULT_UTILS_PW_VALIDATION_DETAILS_MUST_CHANGE=Must Change Password: {0}
INFO_RESULT_UTILS_PW_VALIDATION_DETAILS_SECONDS_TO_EXP=Seconds Until \
Expiration: {0,number,0}
INFO_RESULT_UTILS_PW_VALIDATION_DETAILS_PQR_HEADER=Password Quality \
Requirement Validation Result:
INFO_RESULT_UTILS_PW_VALIDATION_DETAILS_PQR_DESC=Password Quality \
Requirement Description: {0}
INFO_RESULT_UTILS_PW_VALIDATION_DETAILS_PQR_TYPE=Client-Side Validation \
Type: {0}
INFO_RESULT_UTILS_PW_VALIDATION_DETAILS_PQR_PROP=Client-Side Validation \
Property: {0}={1}
INFO_RESULT_UTILS_PW_VALIDATION_DETAILS_PQR_SATISFIED=Requirement Satisfied: \
{0}
INFO_RESULT_UTILS_PW_VALIDATION_DETAILS_PQR_INFO=Additional Validation Info: \
{0}
INFO_RESULT_UTILS_SOFT_DELETE_HEADER=Soft Delete Response Control:
INFO_RESULT_UTILS_SOFT_DELETED_DN=Soft-Deleted Entry DN: {0}
INFO_RESULT_UTILS_TXN_SETTINGS_HEADER=Transaction Settings Response Control:
INFO_RESULT_UTILS_TXN_SETTINGS_NUM_CONFLICTS=Number of Lock Conflicts: \
{0,number,0}
INFO_RESULT_UTILS_TXN_SETTINGS_BACKEND_LOCK_ACQUIRED=Backend Lock Acquired: \
{0}
INFO_RESULT_UTILS_UNIQUENESS_HEADER=Uniqueness Response Control:
INFO_RESULT_UTILS_UNIQUENESS_ID=Uniqueness ID: {0}
INFO_RESULT_UTILS_UNIQUENESS_PRE_COMMIT_STATUS=Pre-Commit Validation Status: \
{0}
INFO_RESULT_UTILS_UNIQUENESS_POST_COMMIT_STATUS=Post-Commit Validation \
Status: {0}
INFO_RESULT_UTILS_UNIQUENESS_MESSAGE=Message: {0}
INFO_RESULT_UTILS_UNIQUENESS_STATUS_VALUE_PASSED=Passed
INFO_RESULT_UTILS_UNIQUENESS_STATUS_VALUE_FAILED=Failed
INFO_RESULT_UTILS_UNIQUENESS_STATUS_VALUE_NOT_ATTEMPTED=Not Attempted
INFO_RESULT_UTILS_SEARCH_REFERENCE_HEADER=Search Result Reference:
INFO_REPORT_BIND_RESULT_HEADER=Bind Result:
INFO_LDAPMODIFY_ARG_GROUP_CONTROLS=Control Arguments
INFO_LDAPMODIFY_ARG_GROUP_DATA=Data Arguments
INFO_LDAPMODIFY_ARG_GROUP_OPS=Operation Arguments
INFO_LDAPMODIFY_TOOL_DESCRIPTION=Applies a set of add, delete, modify, and/or \
modify DN operations to a directory server. The changes to apply should be \
supplied in LDIF format, either via standard input or from a file specified \
with the ''{0}'' argument. Change records must be separated by at least \
one blank line.
INFO_LDAPMODIFY_ARG_DESCRIPTION_ALLOW_UNDELETE=Treat any add operation that \
includes the ''{0}'' attribute as an undelete operation. Undelete requests \
may be used to restore a soft-deleted entry, optionally using a different \
DN than was originally assigned to the entry. The server must be \
configured to allow soft delete operations, and the requester must have the \
soft-delete-read privilege.
INFO_LDAPMODIFY_ARG_DESCRIPTION_ASSURED_REPLICATION=Indicates that all \
operation requests should include the UnboundID-proprietary 'assured \
replication' request control to indicate that the server should delay \
returning a response to the client until a minimum amount of replication \
processing has been performed for the operation. The ''--{0}'', ''--{1}'', \
and ''--{2}'' arguments may be used to configure the settings to use for \
the assured replication control, but the server will automatically \
determine an appropriate value for any argument that is not provided.
INFO_LDAPMODIFY_ARG_DESCRIPTION_AUTHZ_IDENTITY=Indicates that all bind \
requests should include the 'authorization identity' request control as \
defined in RFC 3829. With this control, a successful bind result should \
include the authorization identity assigned to the connection.
INFO_LDAPMODIFY_ARG_DESCRIPTION_CONTINUE_ON_ERROR=Continue processing changes \
even if an error is encountered. If this is not provided, then processing \
will abort after the first failed operation.
INFO_LDAPMODIFY_ARG_DESCRIPTION_DEFAULT_ADD=Assume that any LDIF change \
record without a changeType represents an add operation. If this is not \
provided, then any change record without a changeType will be considered an \
error.
INFO_LDAPMODIFY_ARG_DESCRIPTION_DRY_RUN=Parse the LDIF representations of the \
changes to apply but don't actually perform any LDAP communication.
INFO_LDAPMODIFY_ARG_DESCRIPTION_FOLLOW_REFERRALS=Attempt to follow any \
referrals encountered while processing changes. If this is not provided, \
then any referral received will be considered an error.
INFO_LDAPMODIFY_ARG_DESCRIPTION_GET_AUTHZ_ENTRY_ATTR=Indicates that all bind \
requests should include the UnboundID-proprietary 'get authorization \
entry' request control to request that the server return the specified \
attribute (or collection of attributes, in the case of a special identifier \
like '*' to indicate all user attributes or '+' to indicate all \
operational attributes) from the authenticated user's entry. This argument \
may be provided multiple times to specify multiple attributes to request.
INFO_LDAPMODIFY_ARG_DESCRIPTION_GET_USER_RESOURCE_LIMITS=Indicates that all \
bind requests should include the UnboundID-proprietary 'get user resource \
limits' request control to request that the server return information \
about resource limits (e.g., size limit, time limit, idle time limit, etc.) \
imposed for the user.
INFO_LDAPMODIFY_ARG_DESCRIPTION_HARD_DELETE=Indicates that all delete \
requests should include the UnboundID-proprietary 'hard delete' request \
control, which will permanently delete the target entry even if the \
server would have otherwise performed a soft delete operation to hide the \
entry for a period of time before deleting it.
INFO_LDAPMODIFY_ARG_DESCRIPTION_IGNORE_NO_USER_MOD=Indicates that all add \
requests should include the UnboundID-proprietary 'ignore \
NO-USER-MODIFICATION' request control to permit setting values for certain \
operational attributes not normally permitted to be provided by external \
clients.
INFO_LDAPMODIFY_ARG_DESCRIPTION_LDAP_VERSION=Specifies the LDAP protocol \
version that the tool should use when communicating with the directory \
server. This argument has no effect and is provided only for the purpose \
of compatibility with other ldapmodify tools.
INFO_LDAPMODIFY_ARG_DESCRIPTION_MANAGE_DSA_IT=Indicates that all \
requests should include the manageDsaIT request control to indicate that \
referral entries should be treated as regular entries.
INFO_LDAPMODIFY_ARG_DESCRIPTION_NAME_WITH_ENTRY_UUID=Include the \
UnboundID-proprietary 'name with entryUUID' request control in all add \
requests sent to the server to indicate that the server should use the \
entryUUID operational attribute as the naming attribute for the resulting \
entry instead of the provided RDN.
INFO_LDAPMODIFY_ARG_DESCRIPTION_NO_OPERATION=Include the LDAP no-operation \
control in all add, delete, modify, and modify DN requests sent to the \
server to indicate that the operation should be validated but no changes \
should actually be applied.
INFO_LDAPMODIFY_ARG_DESCRIPTION_PASSWORD_POLICY=Indicates that all add, bind \
and modify requests should include the 'password policy' request control \
(as defined in draft-behera-ldap-password-policy-10) to request that the \
response include password policy-related information about the target entry.
INFO_LDAPMODIFY_PLACEHOLDER_NAME_EQUALS_VALUE={name=value}
INFO_LDAPMODIFY_ARG_DESCRIPTION_PW_UPDATE_BEHAVIOR=Specifies that all add and \
modify requests should include the password update behavior request control \
with the specified behavior. Values for this argument must be in the form \
'name=value', where the property name can be any of the following: \
is-self-change, allow-pre-encoded-password, skip-password-validation, \
ignore-password-history, ignore-minimum-password-age, \
password-storage-scheme, and must-change-password. The value for each \
property should be either 'true' or 'false', with the exception of the \
password-storage-scheme property, whose value should be the name of the \
desired password storage scheme. This argument can be provided multiple \
times to specify multiple password update behaviors.
INFO_LDAPMODIFY_ARG_DESCRIPTION_PASSWORD_VALIDATION_DETAILS=Indicates that \
all add and modify requests that target either the ''{0}'' or ''{1}'' \
attribute should include the UnboundID-proprietary 'password validation \
details' request control to indicate that the response should include \
information about the password quality requirements that the server will \
impose for the target user's password and whether the provided password \
satisfies each of those constraints.
INFO_LDAPMODIFY_ARG_DESCRIPTION_PERMISSIVE_MODIFY=Indicates that all modify \
operation requests should include the 'permissive modify' request \
control, which indicates that the server should be more lenient for certain \
types of changes (e.g., trying to add an attribute value that already \
exists, or trying to remove a value that does not exist) that would \
normally cause the modify operation to be rejected.
INFO_LDAPMODIFY_ARG_DESCRIPTION_PURGE_CURRENT_PASSWORD=Indicates that any \
modify operation that targets either the ''{0}'' or ''{1}'' attribute \
should include the UnboundID-proprietary 'purge current password' request \
control. This will indicate that the server should could purge the \
current password from the entry (even if it would have otherwise been \
retired for a brief period of time).
INFO_LDAPMODIFY_ARG_DESCRIPTION_REPLICATION_REPAIR=Indicates that all \
operation requests should include the UnboundID-proprietary 'replication \
repair' request control. This will cause the change to be applied only to \
the target directory server instance but not to any other server in the \
replication topology.
INFO_LDAPMODIFY_ARG_DESCRIPTION_RETIRE_CURRENT_PASSWORD=Indicates that any \
modify operation that targets either the ''{0}'' or ''{1}'' attribute \
should include the UnboundID-proprietary 'retire current password' \
request control. This will indicate that the server should continue to \
allow the user to authenticate with their current password (in addition to \
the new password) for a brief period of time.
INFO_LDAPMODIFY_ARG_DESCRIPTION_RETRY_FAILED_OPERATIONS=Indicates that, if an \
operation fails in a way that indicates the connection to the server may no \
longer be valid, the tool should automatically create a new connection and \
re-try the operation before reporting it as a failure.
INFO_LDAPMODIFY_ARG_DESCRIPTION_SCRIPT_FRIENDLY=Indicates that the tool \
should operate in script-friendly mode. This argument has no effect and is \
provided only for the purpose of compatibility with other ldapmodify tools.
INFO_LDAPMODIFY_ARG_DESCRIPTION_SOFT_DELETE=Indicates that all delete \
requests should include the UnboundID-proprietary 'soft delete' request \
control, which indicates that the server should hide the entry for a \
period of time before deleting it so that it may be restored with an \
undelete operation if the delete should be reverted.
INFO_LDAPMODIFY_ARG_DESCRIPTION_STRIP_TRAILING_SPACES=Indicates that the tool \
should strip any illegal trailing spaces from LDIF records before \
attempting to process them. If this is not provided, then any LDIF record \
with one or more illegal trailing spaces will be considered an error.
INFO_LDAPMODIFY_ARG_DESCRIPTION_SUBTREE_DELETE=Indicates that all delete \
requests should include the 'subtree delete' request control. In the \
event that the target entry includes one or more subordinate entries, this \
control will indicate that the server should automatically remove all of \
those entries as well. If an entry has one or more subordinates but this \
control is not provided, then an attempt to delete that entry will fail.
INFO_LDAPMODIFY_ARG_DESCRIPTION_SUPPRESS_REFERINT_UPDATES=Indicates that the \
tool should include the UnboundID-proprietary 'suppress referential \
integrity updates' request control in all delete and modify DN operations \
to indicate that the server should not perform any referential integrity \
processing for those operations.
INFO_LDAPMODIFY_ARG_DESCRIPTION_USE_ADMIN_SESSION=Indicates that the tool \
should attempt to use an administrative session to process all operations \
using a dedicated pool of worker threads. This may be useful when trying \
to diagnose problems in a server that is unresponsive because all normal \
worker threads are busy processing other requests.
INFO_LDAPMODIFY_ARG_DESCRIPTION_USE_TRANSACTION=Indicates that the server \
should create a transaction to process all operations as a single atomic \
unit. This should generally only be used with a relatively small number of \
changes, and it is recommended that the changes be supplied in an LDIF file \
rather than via standard input.
INFO_LDAPMODIFY_ARG_DESCRIPTION_ASSURED_REPL_TIMEOUT=Specifies the timeout to \
use for assured replication processing. This should only be used if the \
''{0}'' argument is also provided. If assured replication is to be used \
but this argument is not provided, then the server will automatically \
determine the timeout to use.
INFO_LDAPMODIFY_ARG_DESCRIPTION_UNIQUE_ATTR=Indicates that all add, modify, \
and modify DN requests should include a uniqueness request control that \
indicates that the server should attempt to prevent the requested operation \
from introducing a conflict with the same value in an existing entry. This \
may be provided multiple times to specify multiple unique attribute types, \
and in that case the '--uniquenessMultipleAttributeBehavior' argument may \
be used to specify the behavior to exhibit for conflicts across those \
attribute types.
INFO_LDAPMODIFY_ARG_DESCRIPTION_UNIQUE_FILTER=Indicates that all add, modify \
and modify DN requests should include a uniqueness request control that \
indicates that the server should attempt to prevent the requested \
operation from introducing a conflict with other entries matching the \
provided filter. If the '--uniquenessAttribute' argument is provided, then \
this filter will be used to narrow the set of potentially conflicting \
entries to only those that also match this filter. If the \
'--uniquenessAttribute' argument is not provided, then the server will \
consider it a conflict if any other entry matches the provided filter.
INFO_LDAPMODIFY_ARG_DESCRIPTION_UNIQUE_BASE_DN=Specifies the base DN that \
should be included in the uniqueness request control. This can only be \
used if at least one of the '--uniquenessAttribute' or '--uniquenessFilter' \
arguments is provided. If this is not given, the server will look for \
uniqueness conflicts within all public naming contexts.
INFO_LDAPMODIFY_PLACEHOLDER_BEHAVIOR={behavior}
INFO_LDAPMODIFY_ARG_DESCRIPTION_UNIQUE_MULTIPLE_ATTRIBUTE_BEHAVIOR=Specifies \
the behavior that the server should exhibit if the multiple unique \
attribute types are configured. This can only be used if the \
'--uniquenessAttribute' argument is provided. Allowed values for this \
argument are 'unique-within-each-attribute' (to indicate that each \
attribute should be considered separately), \
'unique-across-all-attributes-including-in-same-entry' (to indicate that \
the value of one unique attribute cannot also be present in the value of \
any other unique attributes, even if the conflicting values are in the same \
entry), 'unique-across-all-attributes-except-in-same-entry' (to indicate \
that the value of one unique attribute cannot also be present in the value \
of any other unique attribute, although the same entry will be permitted to \
have the same value in multiple attributes), or 'unique-in-combination' (to \
indicate that no other entry will be permitted to have the same combination \
of unique attribute values). If this is not specified, then a default \
of 'unique-within-each-attribute' will be used.
INFO_LDAPMODIFY_PLACEHOLDER_LEVEL={level}
INFO_LDAPMODIFY_ARG_DESCRIPTION_UNIQUE_PRE_COMMIT_LEVEL=Specifies the \
level of pre-commit validation that should be used for the uniqueness \
request control. This can only be used if at least one of the \
'--uniquenessAttribute' or '--uniquenessFilter' arguments is provided. \
Allowed values for this argument are 'none' (to indicate that no pre-commit \
validation should be performed), 'all-subtree-views' (to indicate that \
a minimum of one pre-commit check should be performed in each applicable \
subtree view), 'all-backend-sets' (to indicate that a minimum of one \
pre-commit check should be performed in each entry-balancing backend set), \
and 'all-available-backend-servers' (to indicate that the pre-commit check \
should be made in all backend servers available through the Directory Proxy \
Server). If this is not specified, then a default of 'all-subtree-views' \
will be used.
INFO_LDAPMODIFY_ARG_DESCRIPTION_UNIQUE_POST_COMMIT_LEVEL=Specifies the \
level of post-commit validation that should be used for the uniqueness \
request control. This can only be used if at least one of the \
'--uniquenessAttribute' or '--uniquenessFilter' arguments is provided. \
Allowed values for this argument are 'none' (to indicate that no \
post-commit validation should be performed), 'all-subtree-views' (to \
indicate that a minimum of one post-commit check should be performed in \
each applicable subtree view), 'all-backend-sets' (to indicate that a \
minimum of one post-commit check should be performed in each \
entry-balancing backend set), and 'all-available-backend-servers' (to \
indicate that the post-commit check should be made in all backend servers \
available through the Directory Proxy Server). If this is not specified, \
then a default of 'all-subtree-views' will be used.
INFO_LDAPMODIFY_ARG_DESCRIPTION_ADD_CONTROL=Specifies a control that should \
be included in all add requests sent to the server.
INFO_LDAPMODIFY_ARG_DESCRIPTION_BIND_CONTROL=Specifies a control that should \
be included in all bind requests used to authenticate to the server.
INFO_LDAPMODIFY_ARG_DESCRIPTION_DELETE_CONTROL=Specifies a control that \
should be included in all delete requests sent to the server.
INFO_LDAPMODIFY_ARG_DESCRIPTION_MODIFY_CONTROL=Specifies a control that \
should be included in all modify requests sent to the server.
INFO_LDAPMODIFY_ARG_DESCRIPTION_MODIFY_DN_CONTROL=Specifies a control that \
should be included in all modify DN requests sent to the server.
INFO_LDAPMODIFY_ARG_DESCRIPTION_OP_CONTROL=Specifies a control that should be \
included in all add, delete, modify, and modify DN requests sent to the \
server.
INFO_LDAPMODIFY_ARG_DESCRIPTION_LDIF_FILE=The path to the LDIF file \
containing the changes to process. If this is not provided, then the \
changes will be read from standard input. If this argument is provided \
multiple times to supply multiple LDIF files, then they will be processed \
in the order they were provided on the command line.
INFO_LDAPMODIFY_ARG_DESCRIPTION_ENCRYPTION_PW_FILE=The path to a file that \
contains the passphrase used to generate the key used to encrypt the LDIF \
data. If the data is encrypted and this argument is not provided, then the \
tool will interactively prompt for the correct password.
INFO_LDAPMODIFY_PLACEHOLDER_CHARSET={charset}
INFO_LDAPMODIFY_ARG_DESCRIPTION_CHARACTER_SET=The character set for the \
LDIF data to be read. If this argument is not provided, a default encoding \
of UTF-8 will be used.
INFO_LDAPMODIFY_ARG_DESCRIPTION_REJECT_FILE=The path to a file to which \
the tool should write information about any rejected changes.
INFO_LDAPMODIFY_ARG_DESCRIPTION_VERBOSE=Provide verbose output for \
operations processed.
INFO_LDAPMODIFY_ARG_DESCRIPTION_ASSERTION_FILTER=A filter that will be used \
in conjunction with the LDAP assertion request control (as described in RFC \
4528) to indicate that the server should only apply changes to entries that \
match this filter.
INFO_LDAPMODIFY_ARG_DESCRIPTION_MODIFY_ENTRIES_MATCHING_FILTER=Indicates that \
the changes read from standard input or the specified LDIF file should be \
applied to all entries that match the specified filter. Only modify \
operations will be processed when this argument is provided, and the DN of \
the modify change record will be used as the base DN for the search used to \
identify the entries to modify. If the filter may match a large number of \
entries, then it is strongly recommended that the {0} argument be provided \
to process the search in batches. This argument may be provided multiple \
times to specify multiple filters to use to search for entries to modify.
INFO_LDAPMODIFY_ARG_DESCRIPTION_MODIFY_FILTER_FILE=Indicates that the changes \
read from standard input or the specified LDIF file should be applied to \
all entries that match a filter read from the specified file. Only modify \
operations will be processed when this argument is provided, and the DN of \
the modify change record will be used as the base DN for the search used to \
identify the entries to modify. If any of the filters may match a large \
number of entries, then it is strongly recommended that the {0} argument be \
provided to process the search in batches. This argument may be provided \
multiple times to specify multiple filter files to use to search for \
entries to modify.
INFO_LDAPMODIFY_ARG_DESCRIPTION_MODIFY_ENTRY_DN=Indicates that the changes \
read from standard input or the specified LDIF file should be applied to \
the entry with the specified DN rather than the DN contained in the change \
record. Only modify operations will be processed when this argument is \
provided, and it may be provided multiple times to specify the DNs of \
multiple entries to modify.
INFO_LDAPMODIFY_ARG_DESCRIPTION_MODIFY_DN_FILE=Indicates that the changes \
read from standard input or the specified LDIF file should be applied to \
the entries whose DNs are contained in the specified file rather than the \
DN contained in the change record. Only modify operations will be \
processed when this argument is provided, and it may be provided multiple \
times to specify multiple DN files.
INFO_LDAPMODIFY_ARG_DESCRIPTION_SEARCH_PAGE_SIZE=Specifies the page size to \
use in conjunction with the simple paged results control when searching \
for entries to modify based on the filter provided in the {0} or {1} \
argument. If this argument is not provided, then the simple paged results \
control will not be used.
INFO_LDAPMODIFY_ARG_DESCRIPTION_RATE_PER_SECOND=Specifies a maximum operation \
rate that the tool should be permitted to achieve.
INFO_LDAPMODIFY_ARG_DESCRIPTION_ASSURED_REPL_LOCAL_LEVEL=Specifies the local \
assurance level to use for the assured replication request control. This \
should only be used if the ''{0}'' argument is provided. The value \
should be one of 'none', 'received-any-server', or \
'processed-all-servers'. If assured replication is to be used but this \
argument is not provided, then the server will automatically determine the \
local assurance level to use.
INFO_LDAPMODIFY_ARG_DESCRIPTION_ASSURED_REPL_REMOTE_LEVEL=Specifies the \
remote assurance level to use for the assured replication request control. \
This should only be used if the ''{0}'' argument is provided. The value \
should be one of 'none', 'received-any-remote-location', \
'received-all-remote-locations', or 'processed-all-remote-servers'. If \
assured replication is to be used but this argument is not provided, then \
the server will automatically determine the remote assurance level to use.
INFO_LDAPMODIFY_ARG_DESCRIPTION_OPERATION_PURPOSE=Indicates that all \
operations should include the UnboundID-proprietary 'operation purpose' \
request control to provide the specified reason for the operation.
INFO_LDAPSEARCH_NAME_VALUE_PLACEHOLDER={name=value}
INFO_LDAPSEARCH_ARG_DESCRIPTION_OVERRIDE_SEARCH_LIMIT=Indicates that search \
operations should include the override search limits request control with \
the specified name-value pair. This may be provided multiple times to \
specify multiple property name-value pairs to include in the control.
INFO_LDAPMODIFY_ARG_DESCRIPTION_MULTI_UPDATE_ERROR_BEHAVIOR=Indicates that \
all add, delete, modify, and modify DN requests should be sent to the \
server in a single multi-update request with the specified error behavior. \
The value for this argument must be one of 'atomic' (to indicate that all \
updates should be processed atomically so that they will either all \
succeed or all fail), 'abort-on-error' (to indicate that the server \
should only process changes until the first error is encountered and ignore \
any remaining changes after that error), or 'continue-on-error' (to \
indicate that the server should continue attempting to process changes, \
even after one of them has resulted in a failure).
INFO_LDAPMODIFY_ARG_DESCRIPTION_POST_READ_ATTRIBUTE=Indicates that all \
add, modify, and modify DN requests should include the post-read control \
(as described in RFC 4527) to retrieve the value(s) of the specified \
attribute as they appear immediately after the operation has been processed.
INFO_LDAPMODIFY_ARG_DESCRIPTION_PRE_READ_ATTRIBUTE=Indicates that all delete, \
modify, and modify DN requests should include the pre-read control (as \
described in RFC 4527) to retrieve the value(s) of the specified attribute \
as they appear immediately before the operation has been processed.
INFO_LDAPMODIFY_ARG_DESCRIPTION_PROXY_AS=Indicates that all requests should \
include the proxied authorization request control (as described in RFC \
4370) to process the operation under an alternate authorization identity. \
The authorization ID should generally be specified in the form 'dn:' \
followed by the target user's DN, or 'u:' followed by the username.
INFO_LDAPMODIFY_ARG_DESCRIPTION_PROXY_V1_AS=Indicates that all requests \
should include the legacy proxied authorization v1 request control (as \
described in draft-weltman-ldapv3-proxy-04) to process the operation \
under an alternate authorization identity, specified as the DN of the \
desired user.
INFO_LDAPMODIFY_ARG_DESCRIPTION_SUPPRESS_OP_ATTR_UPDATES=Indicates that \
all operations should include the UnboundID-proprietary 'suppress \
operational attribute updates' request control to indicate that the \
server should not apply any updates to the specified operational \
attributes. The value may be one of 'last-access-time', \
'last-login-time', 'last-login-ip', or 'lastmod'.
ERR_LDAPMODIFY_CANNOT_CREATE_CONNECTION_POOL=An error occurred while \
attempting to create a connection pool to communicate with the directory \
server: {0}
INFO_LDAPMODIFY_CONNECTION_ESTABLISHED=Successfully connected to {0}.
INFO_LDAPMODIFY_STARTED_TXN=Successfully started a transaction with ID {0}
ERR_LDAPMODIFY_ENCRYPTION_PW_FILE_EMPTY=Encryption passphrase file ''{0}'' \
is empty.
ERR_LDAPMODIFY_ENCRYPTION_PW_FILE_MULTIPLE_LINES=Encryption passphrase file \
''{0}''has multiple lines. The file must contain exactly one line, which \
is comprised entirely of the encryption passphrase.
ERR_LDAPMODIFY_ENCRYPTION_PW_FILE_READ_ERROR=An error occurred while trying \
to read the encryption passphrase from file ''{0}'': {1}
ERR_LDAPMODIFY_CANNOT_START_TXN=An error occurred while trying to start an \
LDAP transaction: {0}
ERR_LDAPMODIFY_CANNOT_CREATE_LDIF_READER=An error occurred while attempting \
to create an LDIF reader to obtain the changes to process: {0}
ERR_LDAPMODIFY_CANNOT_CREATE_REJECT_WRITER=An error occurred while attempting \
to create a reject writer to write rejected changes to file ''{0}'': {1}
ERR_LDAPMODIFY_IO_ERROR_READING_CHANGE=An I/O error occurred while attempting \
to read an LDIF change record: {0}. It is not possible to continue \
processing changes.
ERR_LDAPMODIFY_RECOVERABLE_LDIF_ERROR_READING_CHANGE=An invalid LDIF change \
record was encountered while reading changes at or near line {0}: {1}. \
That change will be skipped, but the ldapmodify tool will continue trying \
to read additional changes to process.
ERR_LDAPMODIFY_UNRECOVERABLE_LDIF_ERROR_READING_CHANGE=An invalid LDIF change \
record was encountered while reading changes at or near line {0}: {1}. \
That change will be skipped, and the ldapmodify tool cannot continue \
processing changes.
ERR_LDAPMODIFY_INVALID_LINES=The lines that comprise the invalid change \
record are as follows:
ERR_LDAPMODIFY_ERROR_OPENING_FILTER_FILE=An error occurred while attempting \
to open filter file ''{0}'' for reading: {1}
ERR_LDAPMODIFY_IO_ERROR_READING_FILTER_FILE=An I/O error occurred while \
attempting to read from filter file ''{0}'': {1}
ERR_LDAPMODIFY_ERROR_OPENING_DN_FILE=An error occurred while attempting to \
open DN file ''{0}'' for reading: {1}
ERR_LDAPMODIFY_IO_ERROR_READING_DN_FILE=An I/O error occurred while \
attempting to read from filter file ''{0}'': {1}
ERR_LDAPMODIFY_NON_MODIFY_WITH_BULK=Refusing to process a non-modify \
operation when the {0} argument was provided.
ERR_LDAPMODIFY_CANNOT_GET_SEARCH_CONNECTION=Unable to obtain an LDAP \
connection to use to search for entries beneath ''{0}'' that match filter \
''{1}'': {2}
ERR_LDAPMODIFY_SEARCH_FAILED=A search operation used to identify entries \
below ''{0}'' matching filter ''{1}'' returned a non-success result.
ERR_LDAPMODIFY_SEARCH_FAILED_CANNOT_RECONNECT=A search operation used to \
identify entries below ''{0}'' matching filter ''{1}'' returned a \
non-success result indicating that the connection may no longer be valid, \
but it was not possible to obtain a replacement connection to re-try the \
search.
ERR_LDAPMODIFY_CANNOT_DECODE_PAGED_RESULTS_CONTROL=A search operation used to \
identify entries below ''{0}'' matching filter ''{1}'' succeeded, but an \
error occurred while attempting to decode the simple paged results \
response control contained in the search result. Search processing \
cannot continue.
ERR_LDAPMODIFY_MISSING_PAGED_RESULTS_RESPONSE=A search operation used to \
identify entries below ''{0}'' matching filter ''{1}'' succeeded, but the \
search result did not include the expected simple paged results response \
control needed to determine whether there are more entries to be \
processed. Search processing cannot continue.
INFO_LDAPMODIFY_SEARCH_COMPLETED_MORE_PAGES=Completed search processing for \
a page of results for entries below ''{0}'' matching filter ''{1}'', but \
there are still more entries to process. {2,number,0} entries processed \
so far.
INFO_LDAPMODIFY_SEARCH_COMPLETED=Completed search processing for {0,number,0} \
entries below ''{1}'' matching filter ''{2}''.
ERR_LDAPMODIFY_UNSUPPORTED_CHANGE_RECORD_HEADER=Unsupported change record:
INFO_LDAPMODIFY_SENDING_MULTI_UPDATE_REQUEST=Sending the changes to the \
server in a multi-update request ...
INFO_LDAPMODIFY_DRY_RUN_ADD=Would have attempted to add entry {0} if \
argument {1} had not been provided.
INFO_LDAPMODIFY_ADDING_ENTRY=Adding entry {0} ...
INFO_LDAPMODIFY_DRY_RUN_DELETE=Would have attempted to delete entry {0} if \
argument {1} had not been provided.
INFO_LDAPMODIFY_DELETING_ENTRY=Deleting entry {0} ...
INFO_LDAPMODIFY_DRY_RUN_MODIFY=Would have attempted to modify entry {0} if \
argument {1} had not been provided.
INFO_LDAPMODIFY_MODIFYING_ENTRY=Modifying entry {0} ...
INFO_LDAPMODIFY_DRY_RUN_RENAME=Would have attempted to rename entry {0} if \
argument {1} had not been provided.
INFO_LDAPMODIFY_RENAMING_ENTRY=Renaming entry {0} ...
INFO_LDAPMODIFY_DRY_RUN_RENAME_TO=Would have attempted to rename entry {0} to \
{1} if argument {2} had not been provided.
INFO_LDAPMODIFY_RENAMING_ENTRY_TO=Renaming entry {0} to {1} ...
INFO_LDAPMODIFY_DRY_RUN_MOVE=Would have attempted to move entry {0} if \
argument {1} had not been provided.
INFO_LDAPMODIFY_MOVING_ENTRY=Moving entry {0} ...
INFO_LDAPMODIFY_DRY_RUN_MOVE_TO=Would have attempted to move entry {0} to \
{1} if argument {2} had not been provided.
INFO_LDAPMODIFY_MOVING_ENTRY_TO=Moving entry {0} to {1} ...
INFO_LDAPMODIFY_ADD_ADDED_TO_MULTI_UPDATE=Add request for entry {0} added to \
the set of operations to be included in the multi-update request.
INFO_LDAPMODIFY_DELETE_ADDED_TO_MULTI_UPDATE=Delete request for entry {0} \
added to the set of operations to be included in the multi-update request.
INFO_LDAPMODIFY_MODIFY_ADDED_TO_MULTI_UPDATE=Modify request for entry {0} \
added to the set of operations to be included in the multi-update request.
INFO_LDAPMODIFY_MODIFY_DN_ADDED_TO_MULTI_UPDATE=Modify DN request for entry \
{0} added to the set of operations to be included in the multi-update \
request.
INFO_LDAPMODIFY_NO_OP=The operation was accepted by the server but no change \
was applied because the request included the LDAP no-op control.
INFO_LDAPMODIFY_ASSERTION_FAILED=The server refused to process the operation \
because entry ''{0}'' did not match assertion filter ''{1}''.
ERR_LDAPMODIFY_MALFORMED_PW_UPDATE_BEHAVIOR=Value ''{0}'' provided for \
argument ''{1}'' is invalid. The value should be in the form \
''name=value'', where name is one of ''is-self-change'', \
''allow-pre-encoded-password'', ''skip-password-validation'', \
''ignore-password-history'', ''ignore-minimum-password-age'', \
''password-storage-scheme'', or ''must-change-password''. For all \
property names except ''password-storage-scheme'', the value should be \
either ''true'' or ''false'' (for example, ''is-self-change=true''). For \
the ''password-storage-scheme'' property, the value should be the name of \
the desired password storage scheme (for example, \
''password-storage-scheme=PBKDF2'').
ERR_LDAPMODIFY_UNRECOGNIZED_PW_UPDATE_BEHAVIOR=Unrecognized password update \
behavior ''{0}''. The supported behaviors are: ''is-self-change'', \
''allow-pre-encoded-password'', ''skip-password-validation'', \
''ignore-password-history'', ''ignore-minimum-password-age'', \
''password-storage-scheme'', and ''must-change-password''.
ERR_LDAPMODIFY_INVALID_PW_UPDATE_BOOLEAN_VALUE=Invalid value ''{0}'' \
provided for password update behavior property ''{1}''. The value must \
be either ''true'' or ''false''.
ERR_LDAPMODIFY_UNABLE_TO_WRITE_REJECTED_CHANGE=Unable to write information \
about the rejected change to file ''{0}'': {1}
INFO_LDAPMODIFY_EXAMPLE_1=Read the changes to apply from standard input and \
send them to the target directory server over an unencrypted LDAP \
connection. Any change records that don't include a changetype will be \
treated as entries to be added.
INFO_LDAPMODIFY_EXAMPLE_2=Read the changes to apply from the specified LDIF \
and apply them to all entries matching filter '(objectClass=person)' \
using the simple paged results control to retrieve no more than 100 entries \
at a time. The communication will be encrypted with SSL, and if the first \
server is unavailable, the second server will be tried.
ERR_LDAPMODIFY_SEARCH_LISTENER_REFERRAL=A search result reference was \
returned while attempting to modify entries below ''{0}'' matching \
filter ''{1}''. The referral will not be followed. The reference \
included the following referral URL(s): {2}.
INFO_LDAPSEARCH_ARG_GROUP_CONTROLS=Control Arguments
INFO_LDAPSEARCH_ARG_GROUP_DATA=Data Arguments
INFO_LDAPSEARCH_ARG_GROUP_OPS=Operation Arguments
INFO_LDAPSEARCH_ARG_GROUP_TRANSFORMATIONS=Entry Transformation Arguments
INFO_LDAPSEARCH_TOOL_DESCRIPTION=Issues one or more searches to an LDAP \
directory server.
INFO_LDAPSEARCH_ADDITIONAL_DESCRIPTION_PARAGRAPH_1=The criteria for the \
search request can be specified in a number of different ways, including \
providing all of the details directly via command-line arguments, providing \
all of the arguments except the filter via command-line arguments and \
specifying a file that holds the filters to use, or specifying a file that \
includes a set of LDAP URLs with the base DN, scope, filter, and attributes \
to return.
INFO_LDAPSEARCH_ADDITIONAL_DESCRIPTION_PARAGRAPH_2=See the examples below for \
a number of sample command lines for this tool.
INFO_LDAPSEARCH_ARG_DESCRIPTION_ACCOUNT_USABLE=Indicates that all search \
requests should include the UnboundID-proprietary account usable request \
control to request that each search result entry returned include a \
response control with information about the password policy usability \
state for the entry.
INFO_LDAPSEARCH_ARG_DESCRIPTION_AUTHZ_IDENTITY=Indicates that all bind \
requests should include the 'authorization identity' request control as \
defined in RFC 3829. With this control, a successful bind result should \
include the authorization identity assigned to the connection.
INFO_LDAPSEARCH_ARG_DESCRIPTION_CONTINUE_ON_ERROR=Continue processing \
searches even if an error is encountered. If this is not provided, then \
processing will abort after the first failed search.
INFO_LDAPSEARCH_ARG_DESCRIPTION_COUNT_ENTRIES=Indicates that the tool exit \
code should represent the number of entries returned during search \
processing. If this is not provided, or if an error is encountered while \
processing the search, then the tool exit code will reflect the LDAP result \
code received during search processing (or an appropriate client-side \
result code if a problem was encountered before sending any searches). \
Note that because some operating systems do not allow exit code values \
greater than 255, that will be the maximum exit value for this tool even if \
more than 255 entries are returned. Also note that this argument can only \
be used when processing a single search.
INFO_LDAPSEARCH_ARG_DESCRIPTION_WRAP_COLUMN=The column at which long lines in \
the LDIF representation of an entry should be wrapped. A value of zero \
indicates that no wrapping should be performed. If this is not provided, \
then the wrap column will be based on the width of the terminal used to \
run the tool.
INFO_LDAPSEARCH_ARG_DESCRIPTION_DONT_WRAP=Indicates that no line wrapping \
should be performed when displaying the LDIF representations of matching \
entries.
INFO_LDAPSEARCH_ARG_DESCRIPTION_SUPPRESS_BASE64_COMMENTS=Indicates that the \
tool should not include any comments that attempt to provide a \
human-readable representation of any base64-encoded attribute values in \
the search results. If this argument is not provided, then any attribute \
value whose LDIF representation requires base64 encoding will be \
immediately followed by a comment that attempts to provide a human-readable \
representation of the raw bytes that comprise that base64-encoded value.
INFO_LDAPSEARCH_ARG_DESCRIPTION_DRY_RUN=Indicate which searches would be \
issued but do not actually send them to the server.
INFO_LDAPSEARCH_ARG_DESCRIPTION_FOLLOW_REFERRALS=Attempt to follow any \
referrals and search result references encountered during search \
processing. If this is not provided, then referrals and search references \
will be displayed in the output.10
INFO_LDAPSEARCH_ARG_DESCRIPTION_GET_USER_RESOURCE_LIMITS=Indicates that all \
bind requests should include the UnboundID-proprietary 'get user resource \
limits' request control to request that the server return information \
about resource limits (e.g., size limit, time limit, idle time limit, etc.) \
imposed for the user.
INFO_LDAPSEARCH_ARG_DESCRIPTION_INCLUDE_REPL_CONFLICTS=Indicates that all \
search requests should include the UnboundID-proprietary 'return conflict \
entries request control' to indicate that the server may return any \
replication conflict entries that match the search criteria. Replication \
conflict entries are normally excluded from search results.
INFO_LDAPSEARCH_ARG_DESCRIPTION_INCLUDE_SOFT_DELETED=Indicates that all \
search requests should include the UnboundID-proprietary 'soft-deleted \
entry access' request control to indicate that the server may return any \
soft-deleted entries that match the search criteria. Soft-deleted entries \
are normally excluded from search results. The value for this argument \
must be one of: 'with-non-deleted-entries' (indicates that both regular \
and soft-deleted entries should be returned), 'without-non-deleted-entries' \
(indicates that only soft-deleted entries should be returned), or \
'deleted-entries-in-undeleted-form' (returns only soft-deleted entries in \
the form in the form the entry had before it was deleted).
INFO_LDAPSEARCH_ARG_DESCRIPTION_INCLUDE_SUBENTRIES=Indicates that all search \
requests should include the 'subentries' request control (as described \
in draft-ietf-ldup-subentry) to indicate that the server may return any \
LDAP subentries that match the search criteria. LDAP subentries are \
normally excluded from search results.
INFO_LDAPSEARCH_ARG_DESCRIPTION_JOIN_RULE=Indicates that all search requests \
should include the join request control to indicate that matching entries \
should be joined with related entries based on the specified criteria. \
Allowed values include 'dn:' followed by the name of an attribute in the \
source entry containing the DNs of the entries with which to join; \
'reverse-dn:' followed by the name of an attribute in the target entries \
whose value is the DN of the source entry; 'equals:' followed by the \
name of an attribute in the source entry, a colon, and the name of an \
attribute in target entries that must exactly match the source attribute; \
or 'contains:' followed by the name of an attribute in the source entry, a \
colon, and the name of an attribute in target entries that must match or \
contain the value of the source attribute.
INFO_LDAPSEARCH_ARG_DESCRIPTION_JOIN_BASE_DN=Specifies the base DN to use \
for searches used to join search result entries with related entries. \
The value may be one of 'search-base' to use the base DN of the search \
request, 'source-entry-dn' to use the DN of the source entry as the base \
DN for join searches, or any valid LDAP DN to use a custom base DN for join \
searches. If this is not specified, then the default join base DN will be \
the search base DN.
INFO_LDAPSEARCH_ARG_DESCRIPTION_JOIN_SCOPE=Specifies the scope to use for \
searches used to join search result entries with related entries. The \
value may be one of 'base', 'one', 'sub', or 'subordinates'. If this is \
not specified, then the scope of the search request will be used as the \
join scope.
INFO_LDAPSEARCH_ARG_DESCRIPTION_JOIN_SIZE_LIMIT=Specifies the maximum number \
of entries that the server will permit to be joined with any single search \
result entry. If this is not provided, the size limit from the search \
request will be used. Note that the server will impose a maximum join size \
limit of 1000 entries, so any join size limit greater than that will be \
limited to 1000.
INFO_LDAPSEARCH_ARG_DESCRIPTION_JOIN_FILTER=Specifies an additional filter \
that the server will require target entries to match in order to be joined \
with the source entry. If this is not provided, no additional join filter \
will be used.
INFO_LDAPSEARCH_ARG_DESCRIPTION_JOIN_ATTR=Specifies an identifier that \
indicates which attribute(s) should be included in entries joined with \
search result entries. The value may be an attribute name or OID, a \
special token like '*' to indicate all user attributes or '+' to indicate \
all operational attributes, or an object class name prefixed by an '@' \
symbol to indicate all attributes associated with the specified object \
class. This may be provided multiple times to specify multiple requested \
attributes. If this is not specified, then the server will behave as if \
all user attributes had been requested.
INFO_LDAPSEARCH_ARG_DESCRIPTION_JOIN_REQUIRE_MATCH=Indicates that the server \
should not return an entry that matches the search criteria if it is not \
joined with at least one additional entry. If this is not provided, then \
entries matching the search criteria will be returned even if they are not \
joined with any other entries.
INFO_LDAPSEARCH_ARG_DESCRIPTION_MANAGE_DSA_IT=Indicates that all search \
requests should include the manageDsaIT request control to indicate that \
any referral entries in the scope of the search should be treated as \
regular entries rather than causing the server to send search result \
references.
INFO_LDAPSEARCH_ARG_DESCRIPTION_REAL_ATTRS_ONLY=Indicates that all search \
requests should include the UnboundID-proprietary 'real attributes only' \
request control to indicate that the server should not include any \
virtual attributes in entries that are returned.
INFO_LDAPSEARCH_ARG_DESCRIPTION_RETRY_FAILED_OPERATIONS=Indicates that, if a \
search fails in a way that indicates the connection to the server may no \
longer be valid, the tool should automatically create a new connection and \
re-try the search before reporting it as a failure.
INFO_LDAPSEARCH_ARG_DESCRIPTION_SCRIPT_FRIENDLY=Indicates that the tool \
should operate in script-friendly mode. This argument has no effect and is \
provided only for the purpose of compatibility with other ldapsearch tools.
INFO_LDAPSEARCH_ARG_DESCRIPTION_SEPARATE_OUTPUT_FILES=Indicates that the tool \
should generate a separate output file for each search rather than \
combining all results into a single file.
INFO_LDAPSEARCH_ARG_DESCRIPTION_TEE=Indicates that search results should be \
written to standard output as well as to the output file specified via the \
''{0}'' argument.
INFO_LDAPSEARCH_ARG_DESCRIPTION_USE_ADMIN_SESSION=Indicates that the tool \
should attempt to use an administrative session to process all operations \
using a dedicated pool of worker threads. This may be useful when trying \
to diagnose problems in a server that is unresponsive because all normal \
worker threads are busy processing other requests.
INFO_LDAPSEARCH_ARG_DESCRIPTION_SUPPRESS_OP_ATTR_UPDATES=Indicates that \
all operations should include the UnboundID-proprietary 'suppress \
operational attribute updates' request control to indicate that the \
server should not apply any updates to the specified operational \
attributes. The value may be one of 'last-access-time', \
'last-login-time', 'last-login-ip', or 'lastmod'.
INFO_LDAPSEARCH_ARG_DESCRIPTION_PASSWORD_POLICY=Indicates that bind requests \
should include the 'password policy' request control (as defined in \
draft-behera-ldap-password-policy-10) to request that the response include \
password policy-related information about the target entry.
INFO_LDAPSEARCH_ARG_DESCRIPTION_TYPES_ONLY=Indicates that the server should \
only include the names of the attributes contained in the entry rather than \
both names and values.
INFO_LDAPSEARCH_ARG_DESCRIPTION_TERSE=Indicates that the tool should generate \
terse output. The only thing written to standard output will be search \
result entries and references, without any summary messages. Standard \
error will not be affected.
INFO_LDAPSEARCH_ARG_DESCRIPTION_VERBOSE=Indicates that the tool should \
generate verbose output.
INFO_LDAPSEARCH_ARG_DESCRIPTION_VIRTUAL_ATTRS_ONLY=Indicates that all search \
requests should include the UnboundID-proprietary 'virtual attributes \
only' request control to indicate that the server should only include \
virtual attributes in entries that are returned.
INFO_LDAPSEARCH_ARG_DESCRIPTION_BIND_CONTROL=Specifies a control that should \
be included in all bind requests used to authenticate to the server.
INFO_LDAPSEARCH_ARG_DESCRIPTION_SEARCH_CONTROL=Specifies a control that \
should be included in all search requests sent to the server.
INFO_LDAPSEARCH_ARG_DESCRIPTION_BASE_DN=Specifies the base DN that should be \
used for the search. If a filter file is provided, then this base DN will \
be used for each search with a filter read from that file. This argument \
must not be provided if the --ldapURLFile is given. If no base DN is \
specified, then the null base DN will be used by default.
INFO_LDAPSEARCH_ARG_DESCRIPTION_EXCLUDE_BRANCH=Indicates that all search \
requests should include the UnboundID-proprietary 'exclude branch' \
request control to indicate that matching entries below the specified \
base DN should be excluded from search results. This argument may be \
provided multiple times if multiple branches should be excluded.
INFO_LDAPSEARCH_ARG_DESCRIPTION_FILTER_FILE=Specifies the path to a file \
containing the search filters to issue. Each filter should be on a \
separate line. Blank lines and lines beginning with the '#' character \
will be ignored. This argument may be provided multiple times to specify \
multiple filter files. If a filter file is provided, then the first \
trailing argument will not be interpreted as a search filter (all trailing \
arguments will be interpreted as requested attributes).
INFO_LDAPSEARCH_ARG_DESCRIPTION_LDAP_URL_FILE=Specifies the path to a file \
containing LDAP URLs that define the search requests to issue. The LDAP \
URLs will specify the base DN, scope, filter, and attributes to return for \
each search (any hostnames and port numbers included in the URLs will be \
ignored). Each URL should be on a separate line. Blank lines and lines \
beginning with the '#' character will be ignored. This argument may be \
provided multiple times to specify multiple LDAP URL files.
INFO_LDAPSEARCH_ARG_DESCRIPTION_OUTPUT_FORMAT=Specifies the format that \
should be used for the output generated by this tool. Allowed values are \
'LDIF' (LDAP Data Interchange Format, which is the standard string \
representation for LDAP data), 'JSON' (JavaScript Object Notation, which is \
a popular format used by web services), 'CSV' (comma-separated values, \
which is a commonly-used format for text processing, and 'tab-delimited' \
(another commonly-used general text format). If either the 'CSV' or \
'tab-delimited' format is selected, the set of requested attributes must be \
provided with the ''{0}'' argument, the order in which the attributes are \
provided on the command line specifies the order in which they will be \
listed in the output, and if any of those attributes has multiple values \
then only the first value will be used. Further, the 'CSV' and \
'tab-delimited' formats cannot be used in conjunction with the ''{1}'' \
argument. If no output format is specified, a default of 'LDIF' will be \
used.
INFO_LDAPSEARCH_ARG_DESCRIPTION_OUTPUT_FILE=Specifies the path to the file to \
which search results should be written. If this argument is not provided \
then results will be written to standard output.
INFO_LDAPSEARCH_ARG_DESCRIPTION_COMPRESS_OUTPUT=Indicates that the output \
should be gzip-compressed. This can only be used if the --outputFile \
argument is provided and the --teeResultsToStandardOut argument is not \
provided.
INFO_LDAPSEARCH_ARG_DESCRIPTION_ENCRYPT_OUTPUT=Indicates that the output \
should be encrypted with a key generated from a provided password. This \
can only be used if the --outputFile argument is provided and the \
--teeResultsToStandardOut argument is not provided. If the \
--encryptionPassphraseFile argument is provided, then that file will be used \
to specify the encryption passphrase; otherwise, the passphrase will be \
interactively requested.
INFO_LDAPSEARCH_ARG_DESCRIPTION_ENCRYPTION_PW_FILE=The path to a file that \
specifies the passphrase to use to encrypt the output. This can only be \
provided if the --encryptOutput argument is given, but if that argument is \
given and no passphrase file is specified, then the passphrase will be \
interactively requested. If a file is specified, then that file must \
exist and must contain exactly one line comprised entirely of the passphrase.
INFO_LDAPSEARCH_ARG_DESCRIPTION_ASSERTION_FILTER=A filter that will be used \
in conjunction with the LDAP assertion request control (as described in RFC \
4528) to indicate that the server should only process searches in which the \
entry specified as the base DN matches this filter.
INFO_LDAPSEARCH_ARG_DESCRIPTION_FILTER=Specifies a filter to use when \
processing a search. This may be provided multiple times to issue multiple \
searches with different filters. If this argument is provided, then the \
first trailing argument will not be interpreted as a search filter (all \
trailing arguments will be interpreted as requested attributes).
INFO_LDAPSEARCH_ARG_DESCRIPTION_MATCHED_VALUES_FILTER=Indicates that all \
search requests should include the 'matched values' request control (as \
described in RFC 3876) to indicate that search result entries should only \
include values for a given attribute that match the provided filter. This \
argument may be provided multiple times to specify multiple matched values \
filters.
INFO_LDAPSEARCH_ARG_DESCRIPTION_RATE_PER_SECOND=Specifies a maximum search \
rate that the tool should be permitted to achieve. Note that this limit \
applies only to the rate at which the client issues search requests and not \
to the rate at which the server may send matching entries.
INFO_LDAPSEARCH_ARG_DESCRIPTION_PAGE_SIZE=Indicates that all search requests \
should include the 'simple paged results' control (as described in RFC \
2696) to indicate that the search should return entries in pages of no more \
than the specified size. This can be useful for searches that must return \
a large number of entries but the server restricts the number of entries \
that may be returned for any search.
INFO_LDAPSEARCH_ARG_DESCRIPTION_SIZE_LIMIT=Specifies the maximum number of \
entries that the server should return for each search. A value of zero \
(which is the default if this argument is not used) indicates that no \
client-side size limit should be imposed. Note that the server may impose \
its own limit on the number of entries that may be returned for a search.
INFO_LDAPSEARCH_ARG_DESCRIPTION_TIME_LIMIT=Specifies the maximum length of \
time in seconds that the server should spend processing each search. A \
value of zero (which is the default if this argument is not provided) \
indicates that no client-side time limit should be imposed. Note that the \
server may impose its own time limit for search requests.
INFO_LDAPSEARCH_ARG_DESCRIPTION_SCOPE=Specifies the scope that to use for \
search requests. The value should be one of 'base', 'one', 'sub', or \
'subordinates'. If this argument is not provided, a default of 'sub' \
will be used.
INFO_LDAPSEARCH_ARG_DESCRIPTION_DEREFERENCE_POLICY=Specifies the alias \
dereferencing policy to use for search requests. The value should be one \
of 'never', 'always', 'search', or 'find'. If this argument is not \
provided, a default of 'never' will be used.
INFO_LDAPSEARCH_ARG_DESCRIPTION_GET_AUTHZ_ENTRY_ATTR=Indicates that all bind \
requests should include the UnboundID-proprietary 'get authorization \
entry' request control to request that the server return the specified \
attribute (or collection of attributes, in the case of a special identifier \
like '*' to indicate all user attributes or '+' to indicate all \
operational attributes) from the authenticated user's entry. This argument \
may be provided multiple times to specify multiple attributes to request.
INFO_LDAPSEARCH_ARG_DESCRIPTION_GET_EFFECTIVE_RIGHTS_ATTR=Indicates that all \
search requests should include the UnboundID-proprietary 'get effective \
rights' request control to return information about the access control \
rights that a user has when interacting with each matching entry. This \
argument may be provided multiple times to specify multiple attributes.
INFO_LDAPSEARCH_ARG_DESCRIPTION_GET_EFFECTIVE_RIGHTS_AUTHZID=Indicates that \
all search requests should include the UnboundID-proprietary 'get \
effective rights' request control to return information about the \
access control rights the specified user has when interacting with each \
matching entry.
INFO_LDAPSEARCH_ARG_DESCRIPTION_MATCHING_ENTRY_COUNT_CONTROL=Indicates that \
all search requests should include the UnboundID-proprietary 'matching \
entry count' request control, which indicates that the server should \
return information about the number of entries that match the search \
criteria. The maximum number of entries to examine must be specified, \
which helps indicate whether an exact count or an estimate will be \
returned. If alwaysExamine is specified and the number of candidates is \
less than the examine count, then each candidate will be examined to verify \
that it matches the criteria and would actually be returned to the client \
in a search. If allowUnindexed is specified, then the count will be \
allowed to be processed even if the search is unindexed (and may take a \
very long time to complete). If debug is specified, then additional debug \
information may be included in the output.
INFO_LDAPSEARCH_ARG_DESCRIPTION_OPERATION_PURPOSE=Indicates that all search \
requests should include the UnboundID-proprietary 'operation purpose' \
request control to provide the specified reason for the operation.
INFO_LDAPSEARCH_ARG_DESCRIPTION_PERSISTENT_SEARCH=Indicates that the search \
request should include the persistent search request control (as described \
in draft-ietf-ldapext-psearch) to indicate that the server should return \
information about changes to entries that match the search criteria as \
they are processed. This argument may only be used when processing a \
single search operation.
INFO_LDAPSEARCH_ARG_DESCRIPTION_PROXY_AS=Indicates that all search requests \
should include the proxied authorization request control (as described in \
RFC 4370) to process the operation under an alternate authorization \
identity. The authorization ID should generally be specified in the form \
'dn:' followed by the target user's DN, or 'u:' followed by the username.
INFO_LDAPSEARCH_ARG_DESCRIPTION_PROXY_V1_AS=Indicates that all search \
requests should include the legacy proxied authorization v1 request control \
(as described in draft-weltman-ldapv3-proxy-04) to process the search under \
an alternate authorization identity, specified as the DN of the desired user.
INFO_LDAPSEARCH_ARG_DESCRIPTION_REQUESTED_ATTR=Specifies an identifier that \
indicates which attribute(s) should be included in entries that match the \
search criteria. The value may be an attribute name or OID, a special \
token like '*' to indicate all user attributes or '+' to indicate all \
operational attributes, or an object class name prefixed by an '@' symbol \
to indicate all attributes associated with the specified object class. \
This may be provided multiple times to specify multiple requested \
attributes, and it may be provided instead of or in addition to the set of \
requested attributes in the set of trailing arguments. If this is not \
specified, then the server will behave as if all user attributes had been \
requested.
INFO_LDAPSEARCH_ARG_DESCRIPTION_SORT_ORDER=Indicates that all search requests \
should include the server-side sort request control (as described in RFC \
2891) to request that the server sort results before returning them to the \
client. The sort order should be a comma-separated list of attribute \
names, each of which may be optionally prefixed by '+' (to indicate that \
sorting should be in ascending order for that attribute) or '-' (for \
descending order), and may be optionally followed by a colon and the name \
or OID for the ordering matching rule that should be used when sorting. \
Ascending order will be used if neither '+' or '-' is specified, and if no \
matching rule ID is given then the attribute type's own ordering rule will \
be used.
INFO_LDAPSEARCH_ARG_DESCRIPTION_VLV=Indicates that all search requests should \
include the virtual list view (VLV) request control (as described in \
draft-ietf-ldapext-ldapv3-vlv) to indicate that the server should return \
the specified subset of the sorted search results (and the ''{0}'' argument \
must also be given to specify the sort order). The value should be a \
colon-delimited list indicating which page of results to return, and it may \
take one of two forms. In either case, the first element specifies the \
number of elements to return before the entry identified as the start of \
the results, and the second is the number of entries after the "start" \
entry. The third element identifies the start of the result set, and it \
may be either an integer offset (in which the first entry in the result \
set has an offset of one), or a string that provides a value for which the \
server should identify the first entry whose value for the primary sort \
attribute is greater than or equal to the given string. In the event that \
an offset is provided, a fourth element must also be given to indicate the \
expected number of entries in the result set, or zero if that is not \
known. For example, a value of '0:9:1:0' indicates that the server should \
return the first ten entries of the result set (starting at offset 1, which \
is the first entry, return the zero previous entries and the nine following \
entries, with no indication of how many entries match the search \
criteria). Alternately, a value of '0:99:smith' indicates that the server \
should the first 100 entries in the result set for which the primary sort \
attribute has a value that is greater than or equal to 'smith'.
INFO_LDAPSEARCH_ARG_DESCRIPTION_REJECT_UNINDEXED_SEARCH=Indicates that all \
search requests should include the UnboundID-proprietary reject unindexed \
search request control to indicate that the server should not process the \
search operation if it cannot do so efficiently using server indexes, even \
if the requester has the unindexed-search privilege.
INFO_LDAPSEARCH_ARG_DESCRIPTION_PERMIT_UNINDEXED_SEARCH=Indicates that all \
search requests should include the UnboundID-proprietary permit unindexed \
search request control to indicate that the server should process the \
search operation even if it cannot do so efficiently using server indexes. \
The requester must have either the unindexed-search or \
unindexed-search-with-control privilege.
INFO_LDAPSEARCH_ARG_DESCRIPTION_EXCLUDE_ATTRIBUTE=Specifies the name or OID \
of an attribute that should be excluded from search result entries. This \
argument may be provided multiple times to specify multiple attributes to \
exclude.
INFO_LDAPSEARCH_ARG_DESCRIPTION_REDACT_ATTRIBUTE=Specifies the name or OID of \
an attribute whose values should be redacted to indicate that the attribute \
is present in search result entries but to hide the actual values for that \
attribute. This argument may be provided multiple times to specify \
multiple attributes to redact.
INFO_LDAPSEARCH_ARG_DESCRIPTION_HIDE_REDACTED_VALUE_COUNT=Indicates that the \
output should not reveal the number of values contained in redacted \
attributes. If this argument is present, then a redacted attribute will \
only ever have a single value of '***REDACTED***'. If this argument is not \
present, then a redacted attribute with multiple values will still have \
the same number of values that it originally had, but those values will \
be '***REDACTED1***', '***REDACTED2***', etc.
INFO_LDAPSEARCH_ARG_DESCRIPTION_SCRAMBLE_ATTRIBUTE=Specifies the name or OID \
of an attribute whose values should be scrambled. Scrambling will be \
performed in a manner that attempts to preserve the associated attribute \
syntax and that will generally try to ensure that a given input value will \
consistently yield the same scrambled output. This argument may be \
provided multiple times to specify multiple attributes to scramble.
INFO_LDAPSEARCH_ARG_DESCRIPTION_SCRAMBLE_JSON_FIELD=Specifies the name of a \
JSON field whose values should be scrambled. If the --scrambleAttribute \
argument is used to scramble any attributes whose values may be JSON \
objects, then all JSON field names will be preserved and only the values of \
the specified fields will be scrambled. If this argument is given (and it \
may be provided multiple times to target multiple JSON fields), then only \
the specified fields will have their values scrambled. If this argument \
is not provided, then any of the scramble attribute values that are JSON \
objects will have all values scrambled. JSON field names will be treated \
in a case-insensitive manner.
INFO_LDAPSEARCH_ARG_DESCRIPTION_SCRAMBLE_RANDOM_SEED=Specifies the value that \
will be used to seed the random number generator used in the course of \
scrambling attribute values. If a random seed is provided, then scrambling \
the same entry with the same seed should consistently yield the same \
scrambled representations. If no random seed is specified, an appropriate \
value will be selected automatically.
INFO_LDAPSEARCH_ARG_DESCRIPTION_RENAME_ATTRIBUTE_FROM=Specifies the name or \
OID of an attribute that should have its name replaced with the value \
specified in the --renameAttributeTo argument. This argument may be \
provided multiple times as long as the --renameAttributeTo argument is also \
provided the same number of times, and the order of --renameAttributeFrom \
values must correspond to the order of --renameAttributeTo values.
INFO_LDAPSEARCH_ARG_DESCRIPTION_RENAME_ATTRIBUTE_TO=Specifies the new name \
to use for an attribute to be renamed. This argument must be provided the \
same number of times as the --renameAttributeFrom argument.
INFO_LDAPSEARCH_ARG_DESCRIPTION_MOVE_SUBTREE_FROM=Specifies the base DN for \
a subtree to be moved to another location in the DIT, with this source DN \
being replaced with the base DN specified using the --moveSubtreeTo \
argument. This argument may be provided multiple times as long as the \
--moveSubtreeTo argument is also provided the same number of times, and the \
order of --moveSubtreeFrom values must correspond to the order of \
--moveSubtreeTo values.
INFO_LDAPSEARCH_ARG_DESCRIPTION_MOVE_SUBTREE_TO=Specifies the new base DN for \
a subtree to be moved. This argument must be provided the same number of \
times as the --moveSubtreeFrom argument.
INFO_LDAPSEARCH_ARG_DESCRIPTION_LDAP_VERSION=Specifies the LDAP protocol \
version that the tool should use when communicating with the directory \
server. This argument has no effect and is provided only for the purpose \
of compatibility with other ldapsearch tools.
INFO_LDAPSEARCH_TRAILING_ARGS_PLACEHOLDER={filter} [{attr1} [{attr2} ...]]
ERR_LDAPSEARCH_TRAILING_ARGS_WITH_URL_FILE=Trailing arguments are not allowed \
when the ''{0}'' argument is provided.
ERR_LDAPSEARCH_TRAILING_FILTER_WITH_FILTER_FILE=If a filter file is \
specified, then a filter cannot be provided as a trailing argument.
ERR_LDAPSEARCH_NO_TRAILING_ARGS=If neither the ''{0}'' nor the ''{1}'' \
argument is provided, the filter to use for the search must be provided as \
a trailing argument.
ERR_LDAPSEARCH_FIRST_TRAILING_ARG_NOT_FILTER=The first trailing argument \
''{0}'' is not a valid LDAP search filter.
WARN_LDAPSEARCH_TRAILING_ARG_STARTS_WITH_DASH=WARNING: Unnamed trailing \
argument ''{0}'' starts with a dash. Trailing arguments should only be \
used for the search filter (unless a different argument is used to specify \
the filters) and set of requested attributes to include in search result \
entries. If this was intended to be a named argument, it should be \
placed earlier in the argument list.
ERR_LDAPSEARCH_INVALID_MATCHED_VALUES_FILTER=Filter ''{0}'' is a valid \
search filter, but is not valid for use with the matched values request \
control.
ERR_LDAPSEARCH_MATCHING_ENTRY_COUNT_INVALID_VALUE=The value provided for the \
''{0}'' argument is invalid. The value must start with 'examineCount=' \
followed by an integer greater than or equal to zero. It may optionally \
also contain ':alwaysExamine' (to indicate that it should always attempt \
to examine candidate entries to determine whether they actually match), \
':allowUnindexed' (to indicate that the server should attempt to \
determine the matching entry count even if the search criteria is not \
indexed), ':skipResolvingExplodedIndexes' (to indicate whether the server \
should skip the effort of actually retrieving the candidate entry IDs for \
exploded index keys in which the number of matching entries is known), \
':fastShortCircuitThreshold=' followed by an integer value (to specify the \
short-circuit threshold that the server should use when determining whether \
to continue with index processing, even if there may be additional filter \
components that may be very fast to process), ':slowShortCircuitThreshold=' \
followed by an integer value (to specify the short-circuit threshold that \
should be used if it is expected that there may be potentially-expensive \
filter components left to evaluate), and/or ':debug' (to indicate that the \
response control should include debug information about the processing \
performed in the course of making the determination.
ERR_LDAPSEARCH_OVERRIDE_LIMIT_NO_EQUAL=A value provided for the ''{0}'' \
argument is invalid because it does not contain an equal sign to separate \
the property name from the value.
ERR_LDAPSEARCH_OVERRIDE_LIMIT_EMPTY_PROPERTY_NAME=A value provided for the \
''{0}'' argument is invalid because it starts with an equal sign, \
indicating an empty property name. Property names must not be empty.
ERR_LDAPSEARCH_OVERRIDE_LIMIT_DUPLICATE_PROPERTY_NAME=A value provided for \
the ''{0}'' argument is invalid because there are multiple attempts to set \
a value for property ''{1}''. The same property cannot be set multiple \
times.
ERR_LDAPSEARCH_OVERRIDE_LIMIT_EMPTY_PROPERTY_VALUE=A value provided for the \
''{0}'' argument is invalid because it contains an empty value for property \
''{1}''. Property values must not be empty.
ERR_LDAPSEARCH_PERSISTENT_SEARCH_INVALID_VALUE=The value provided for the \
''{0}'' argument is invalid. The value must start with 'ps'. That may be \
followed by a colon and a comma-delimited list of change types ('add', \
'delete', 'modify', or 'modifydn'), or 'any' to indicate that all change \
types should be included. That may be followed by a colon and a '1' to \
indicate that the search should only return matching entries when they are \
targeted by an appropriate operation, or '0' to indicate that the search \
should first return all existing entries that match the criteria before \
transitioning to returning to returning entries as updates occur. That may \
be followed by a colon and a '1' to request that the server include entry \
change notification controls with search result entries, or '0' to request \
no such controls. A value of just 'ps' is equivalent to 'ps:any:1:1'.
ERR_LDAPSEARCH_SORT_ORDER_INVALID_VALUE=The value provided for the ''{0}'' \
argument is invalid. The value must be a comma-delimited list of one or \
more attribute names or OIDs, each of which may be prefixed by '-' to \
indicate that sorting for that attribute should be in descending order, or \
'+' to indicate that sorting for that attribute should be in ascending \
order. If an attribute name is not prefixed with either '-' or '+', then \
sorting for that attribute will be in ascending order.
ERR_LDAPSEARCH_VLV_INVALID_VALUE=The value provided for the ''{0}'' argument \
is invalid. The value must either be a colon-delimited list of four \
integers (representing the before count; after count; offset index; and \
expected result set size, with zero used if the expected result set size is \
not known), or a colon-delimited list of two integers and one string \
(representing the before count, after count, and the primary sort attribute \
value that should be used as the start of the result set).
ERR_LDAPSEARCH_JOIN_RULE_INVALID_VALUE=The value provided for the ''{0}'' \
argument is invalid. The value must be one of the following: the string \
'dn:' followed by the name or OID of an attribute in the source entry whose \
values are the DNs of the entries with which to join; the string \
'reverse-dn:' followed by the name or OID of an attribute in the target \
entry with a value that matches the DN of the source entry; the string \
'equals:' followed by the name or OID of an attribute in the source entry, \
a colon, and the name or OID of an attribute in target entries that must \
have a value that equals at least one value of the source attribute; or the \
string 'contains:' followed by the name or OID of an attribute in the \
source entry, a colon, and the name or OID of an attribute in target \
entries that must have a value that matches or contains as a substring at \
least one value of the source attribute.
ERR_LDAPSEARCH_JOIN_BASE_DN_INVALID_VALUE=The value provided for the ''{0}'' \
argument is invalid. The value may be 'search-base' to use the base DN \
from the search request as the base DN for join searches, 'source-entry-dn' \
to use the DN of the source entry as the base DN for join searches, or any \
valid DN to use that DN as the base DN for join searches.
ERR_LDAPSEARCH_RENAME_ATTRIBUTE_MISMATCH=The --renameAttributeFrom argument \
must be provided the same number of times as the --renameAttributeTo \
argument.
ERR_LDAPSEARCH_MOVE_SUBTREE_MISMATCH=The --moveSubtreeFrom argument must be \
provided the same number of times as the --moveSubtreeTo argument.
ERR_LDAPSEARCH_OUTPUT_FORMAT_NOT_SUPPORTED_WITH_URLS=The ''{0}'' output \
format cannot be used in conjunction with the ''{1}'' argument.
ERR_LDAPSEARCH_OUTPUT_FORMAT_REQUIRES_REQUESTED_ATTR_ARG=The ''{0}'' output \
format requires that the set of requested arguments be identified with the \
''{1}'' argument rather than as unnamed trailing arguments.
ERR_LDAPSEARCH_CANNOT_OPEN_OUTPUT_FILE=Unable to open output file ''{0}'' \
for writing: {1}
ERR_LDAPSEARCH_CANNOT_CREATE_CONNECTION_POOL=An error occurred while \
attempting to create a connection pool to communicate with the directory \
server: {0}
ERR_LDAPSEARCH_MALFORMED_LDAP_URL=LDAP URL file ''{0}'' contains value \
''{1}'' that cannot be parsed as a valid LDAP URL.
ERR_LDAPSEARCH_CANNOT_READ_LDAP_URL_FILE=An error occurred while attempting \
to read from LDAP URL file ''{0}'': {1}
ERR_LDAPSEARCH_MALFORMED_FILTER=Filter file ''{0}'' contains a value that \
cannot be parsed as a valid LDAP search filter: {1}
ERR_LDAPSEARCH_CANNOT_READ_FILTER_FILE=An error occurred while attempting \
to read from filter URL file ''{0}'': {1}
INFO_LDAPSEARCH_DRY_RUN_REQUEST_NOT_SENT=No search operation was actually \
processed because the {0} argument was provided. The request that would \
have been sent is: {1}
INFO_LDAPSEARCH_SENDING_SEARCH_REQUEST=Sending search request {0}
ERR_LDAPSEARCH_MISSING_PAGED_RESULTS_RESPONSE_CONTROL=The search request \
included the simple paged results request control, but the corresponding \
search result did not include the expected response control. It is not \
possible to continue paging through the search results.
ERR_LDAPSEARCH_CANNOT_DECODE_PAGED_RESULTS_RESPONSE_CONTROL=An error occurred \
while attempting to decode the simple paged results response control \
included in the search result: {0}. It is not possible to continue \
paging through the search results.
INFO_LDAPSEARCH_INTERMEDIATE_PAGED_SEARCH_RESULT=Intermediate search result \
with more pages to retrieve:
INFO_LDAPSEARCH_TOTAL_SEARCH_ENTRIES=Total Entries Returned: {0,number,0}
INFO_LDAPSEARCH_TOTAL_SEARCH_REFERENCES=Total References Returned: \
{0,number,0}
INFO_LDAPSEARCH_EXAMPLE_1=Establishes an unencrypted LDAP connection to \
directory.example.com:389, performs a simple bind to authenticate as user \
'uid=jdoe,ou=People,dc=example,dc=com', and issues a search request to \
retrieve the givenName, sn, and mail attributes for the user with uid \
'jqpublic' below dc=example,dc=com. The search results will be written to \
standard output.
INFO_LDAPSEARCH_EXAMPLE_2=Establishes an SSL-encrypted LDAP connection to \
directory.example.com:636, interactively prompting the user about whether \
to trust the certificate presented by the directory server. The tool \
will then bind with the SASL PLAIN mechanism using an authentication ID of \
"u:jdoe" and a password read from a file. It will then issue a search \
request for each filter in a given file, writing the results for each \
search into a separate output file.
INFO_LDAPSEARCH_EXAMPLE_3=Establishes an LDAP connection to \
directory.example.com:389 that is secured with the StartTLS extended \
operation, using the information in the provided trust store file to \
determine whether to trust the certificate presented by the directory \
server. It will then issue an unauthenticated search to retrieve all \
user and operational attributes from the server's root DSE. The output \
will be written to a specified output file as well as displayed on standard \
output.
INFO_LDAPSEARCH_EXAMPLE_4=Issues a search request to retrieve all entries at \
or below 'dc=example,dc=com', using the simple paged results control to \
retrieve up to 100 entries at a time. The search will use an unencrypted \
LDAP connection, and the tool will interactively prompt the user for the \
password to use when performing simple authentication.
INFO_LDAPSEARCH_EXAMPLE_5=Issues a search request to retrieve a \
special entry that provides details about the server's use of indexes to \
determine the candidate set of potential matching entries. This feature \
is only supported in the UnboundID/Ping Identity Directory Server, and \
the user must have access control rights to retrieve the 'cn=debugsearch' \
entry and the 'debugsearchindex' operational attribute.
INFO_SPLIT_LDIF_TOOL_DESCRIPTION=Splits a single LDIF file into multiple \
sets by separating entries below a specified base DN into different \
mutually-exclusive collections of entries. A number of algorithms are \
available to determine how entries should be split, and entries outside the \
split base DN may be included in all sets or added to a dedicated LDIF file.
INFO_SPLIT_LDIF_GLOBAL_ARG_DESC_SOURCE_LDIF=The path to an LDIF file \
containing the data to be split into multiple sets. This argument may be \
provided multiple times to specify multiple LDIF files, and the files will \
be processed in the order they were provided on the command line.
INFO_SPLIT_LDIF_GLOBAL_ARG_DESC_SOURCE_COMPRESSED=Indicates that the source \
LDIF files are gzip-compressed.
INFO_SPLIT_LDIF_GLOBAL_ARG_DESC_TARGET_LDIF_BASE=The path and base name to \
use for the LDIF files containing the data that has been split. The \
resulting LDIF files will use this path with different extensions ('.set1' \
for the first set, '.set2' for the second set, and so on, and \
'.outside-split-base-dn' if a file is to be created to hold entries that \
exist outside of the split base DN). If this is not provided, then the \
source LDIF path will be used as the base name.
INFO_SPLIT_LDIF_GLOBAL_ARG_DESC_COMPRESS_TARGET=Indicates that the target \
LDIF files should be gzip-compressed.
INFO_SPLIT_LDIF_GLOBAL_ARG_DESC_ENCRYPT_TARGET=Indicates that the target LDIF \
LDIF files should be encrypted with a key generated from a provided \
passphrase. If the --encryptionPassphraseFile argument is provided, then \
the passphrase will be read from the specified file. Otherwise, it will be \
interactively requested from the user.
INFO_SPLIT_LDIF_GLOBAL_ARG_DESC_ENCRYPT_PW_FILE=The path to the file \
containing the passphrase to use to generate the encryption key. This \
passphrase will be used to decrypt the input (if it is encrypted) and to \
encrypt the output (if it is to be encrypted). If this is not provided and either the input or output is encrypted, then the passphrase will be \
interactively requested. If it is provided, then the specified file must \
exist and must contain exactly one line that is comprised entirely of the \
encryption passphrase.
INFO_SPLIT_LDIF_GLOBAL_ARG_DESC_SPLIT_BASE_DN=The base DN below which entries \
should be split. The entry with this DN will appear in all sets, but each \
entry below this base DN will appear in exactly one set. This must be \
provided.
INFO_SPLIT_LDIF_GLOBAL_ARG_DESC_OUTSIDE_TO_ALL_SETS=Indicates that entries \
outside the split base DN should be added to all sets containing split data.
INFO_SPLIT_LDIF_GLOBAL_ARG_DESC_OUTSIDE_TO_DEDICATED_SET=Indicates that \
entries outside the split base DN should be added to a dedicated set in its \
own file.
INFO_SPLIT_LDIF_GLOBAL_ARG_DESC_SCHEMA_PATH=The path to a file or directory \
from which to read schema definitions to use when processing. If the \
provided path is a file, then it must be an LDIF file containing the \
definitions to read. If the provided path is a directory, then schema \
definitions will be read from all files with an extension of '.ldif' in \
that directory. If this argument is provided multiple times, then the \
paths will be processed in the order they were provided on the command \
line. If this argument is not provided, then a default standard schema \
will be used.
INFO_SPLIT_LDIF_GLOBAL_ARG_DESC_NUM_THREADS=The number of threads to use when \
processing. If this is not specified, a single thread will be used.
INFO_SPLIT_LDIF_SC_HASH_ON_RDN_DESC=Splits the data by computing a hash on \
the normalized representation of the DN component immediately below the \
split base DN, and using a modulus operation to determine the set in which \
to place the entry. This split algorithm does not require any caching to \
ensure that a subordinate entry is placed in the same set as its parent.
INFO_SPLIT_LDIF_SC_HASH_ON_RDN_ARG_DESC_NUM_SETS=The number of sets into \
which the data should be split. This must be provided, and the value must \
be greater than or equal to two.
INFO_SPLIT_LDIF_SC_HASH_ON_RDN_EXAMPLE=Splits LDIF file 'whole.ldif' so that \
entries below 'ou=People,dc=example,dc=com' will be split into four sets, \
selected by computing a digest of the RDN component immediately below \
'ou=People,dc=example,dc=com', with names starting with 'split.ldif'.
INFO_SPLIT_LDIF_SC_HASH_ON_ATTR_DESC=Splits the data by computing a hash on \
the value(s) of a specified attribute in entries immediately below the \
split base DN, and using a modulus operation to determine the set in which \
to place the entry. If an entry does not contain the target attribute, the \
set will be chosen based on a hash of the DN component immediately below \
the split base DN. Unless the --assumeFlatDIT argument is provided, a \
cache will be used to ensure that subordinate entries are added into the \
same set as their parents.
INFO_SPLIT_LDIF_SC_HASH_ON_ATTR_ARG_DESC_ATTR_NAME=The name or OID of the \
attribute for which to compute the hash. This must be provided.
INFO_SPLIT_LDIF_SC_HASH_ON_ATTR_ARG_DESC_NUM_SETS=The number of sets into \
which the data should be split. This must be provided, and the value must \
be greater than or equal to two.
INFO_SPLIT_LDIF_SC_HASH_ON_ATTR_ARG_DESC_ALL_VALUES=Indicates that the \
hashing process should examine all values for the target attribute. If \
this argument is not provided, then only the first value for the attribute \
will be used to determine the set in which an entry should be placed.
INFO_SPLIT_LDIF_SC_HASH_ON_ATTR_ARG_DESC_ASSUME_FLAT_DIT=Indicates that the \
tool should assume that all entries below the split base DN will be exactly \
one level below that entry, so that it is not necessary to maintain a cache \
to determine where a subordinate entry's parent resides. If this argument \
is provided but one or more subordinate entries are found, then then will \
be added to a separate file so the appropriate set can be manually \
identified.
INFO_SPLIT_LDIF_SC_HASH_ON_ATTR_EXAMPLE=Splits LDIF file 'whole.ldif' so that \
entries below 'ou=People,dc=example,dc=com' will be split into four sets, \
selected by computing a digest of the first value of the 'uid' attribute, \
with names starting with 'split.ldif'.
INFO_SPLIT_LDIF_SC_FEWEST_ENTRIES_DESC=Splits the data by selecting the \
set with the fewest number of entries. When processing data in a flat DIT, \
this will essentially be a round-robin distribution. When processing data \
in a DIT with branches of varying sizes, this can help ensure that the \
resulting LDIF files will have roughly the same number of entries (although \
running the tool with multiple threads may make this less accurate). \
Unless the --assumeFlatDIT argument is provided, a cache will be used to \
ensure that subordinate entries are added into the same set as their parents.
INFO_SPLIT_LDIF_SC_FEWEST_ENTRIES_ARG_DESC_NUM_SETS=The number of sets into \
which the data should be split. This must be provided, and the value must \
be greater than or equal to two.
INFO_SPLIT_LDIF_SC_FEWEST_ENTRIES_ARG_DESC_ASSUME_FLAT_DIT=Indicates that the \
tool should assume that all entries below the split base DN will be exactly \
one level below that entry, so that it is not necessary to maintain a cache \
to determine where a subordinate entry's parent resides. If this argument \
is provided but one or more subordinate entries are found, then then will \
be added to a separate file so the appropriate set can be manually \
identified.
INFO_SPLIT_LDIF_SC_FEWEST_ENTRIES_EXAMPLE=Splits LDIF file 'whole.ldif' into \
four sets, with names starting with 'split.ldif', so that each entry \
immediately below 'ou=People,dc=example,dc=com' will be placed in the set \
that currently has the fewest entries.
INFO_SPLIT_LDIF_SC_FILTER_DESC=Splits the data by using search filters to \
select the appropriate set. The filters will be evaluated in the order \
they were provided on the command line, and the entry will be added to the \
first set for which a matching filter is found. If the entry doesn't match \
any of the provided filters, then the appropriate set will be determined by \
computing a hash on the RDN. Unless the --assumeFlatDIT argument is \
provided, a cache will be used to ensure that subordinate entries are added \
into the same set as their parents.
INFO_SPLIT_LDIF_SC_FILTER_ARG_DESC_FILTER=A filter to evaluate against \
entries exactly one level below the split base DN to determine which set \
should be used to hold the entry. This argument should be provided \
multiple times, once for each set into which the data should be split, and \
the filters will be evaluated in the order they were provided on the \
command line until one is found that matches the target entry.
INFO_SPLIT_LDIF_SC_FILTER_ARG_DESC_ASSUME_FLAT_DIT=Indicates that the tool \
should assume that all entries below the split base DN will be exactly one \
level below that entry, so that it is not necessary to maintain a cache to \
determine where a subordinate entry's parent resides. If this argument is \
provided but one or more subordinate entries are found, then then will be \
added to a separate file so the appropriate set can be manually identified.
INFO_SPLIT_LDIF_SC_FILTER_EXAMPLE=Splits LDIF file 'whole.ldif' into four \
sets, with names starting with 'split.ldif', so that each entry \
immediately below 'ou=People,dc=example,dc=com' will be selected by \
matching that entry against a search filter. Entries matching \
'(timeZone=Eastern)' will go into the first set, entries matching \
'(timeZone=Central)' into the second set, '(timeZone=Mountain)' into the \
third set, and '(timeZone=Pacific)' into the fourth. Any entries not \
matching any of those filters will be placed by computing a hash on its RDN.
ERR_SPLIT_LDIF_NO_TARGET_BASE_PATH=If the {0} argument is provided multiple \
times, then the {1} argument must also be provided to specify the base \
path and name for the file to be written.
ERR_SPLIT_LDIF_NON_UNIQUE_FILTER=All values provided for the ''{0}'' argument \
must be unique. Filter ''{1}'' was provided multiple times.
ERR_SPLIT_LDIF_NOT_ENOUGH_FILTERS=If the ''{0}'' subcommand is used, the \
''{1}'' argument must be provided multiple times, with each occurrence \
defining the criteria for a different set.
ERR_SPLIT_LDIF_CANNOT_DETERMINE_SPLIT_ALGORITHM=Unable to determine which \
algorithm should be used to split the data. One of the following \
subcommands must be used to specify the algorithm: {0}
ERR_SPLIT_LDIF_ERROR_CREATING_LDIF_READER=An error occurred while attempting \
to create the LDIF reader: {0}
ERR_SPLIT_LDIF_INVALID_LDIF_RECORD_RECOVERABLE=A malformed LDIF record was \
encountered while in the source data: {0}. This record will be skipped, \
but processing will continue.
ERR_SPLIT_LDIF_INVALID_LDIF_RECORD_UNRECOVERABLE=A malformed LDIF record was \
encountered while in the source data: {0}. Processing cannot continue.
ERR_SPLIT_LDIF_IO_READ_ERROR=An I/O error occurred while attempting \
to read the source data: {0}. Processing cannot continue.
ERR_SPLIT_LDIF_UNEXPECTED_READ_ERROR=An unexpected error was encountered \
while attempting to read the source data: {0}. Processing cannot continue.
ERR_SPLIT_LDIF_ENTRY_WITHOUT_PARENT=Unable to determine which set should hold \
entry ''{0}'' because it is more than one level below split base DN ''{1}'' \
but one or more of its superiors does not exist in the LDIF file.
INFO_SPLIT_LDIF_PROGRESS=Processed {0,number,0} entries
ERR_SPLIT_LDIF_CANNOT_OPEN_OUTPUT_FILE=An error occurred while attempting to \
open output file ''{0}'' for writing: {1}
ERR_SPLIT_LDIF_ERROR_WRITING_ERROR_TO_FILE=An error occurred while attempting \
to write information about error ''{0}'' to output file ''{1}'': {2}
ERR_SPLIT_LDIF_ERROR_WRITING_TO_FILE=An error occurred while attempting to \
write entry ''{0}'' to output file ''{1}'': {2}
INFO_SPLIT_LDIF_PROCESSING_COMPLETE=Processing complete. Read {0,number,0} \
entries.
INFO_SPLIT_LDIF_EXCLUDED_COUNT=Excluded {0,number,0} entries that were not \
within the split base DN.
INFO_SPLIT_LDIF_COUNT_TO_FILE=Wrote {0,number,0} entries to file {1}.
ERR_SPLIT_LDIF_ERROR_CLOSING_FILE=An error was encountered while attempting \
to close output file ''{0}'': {1}. The file may be incomplete.
ERR_SPLIT_LDIF_NO_SCHEMA_FILES=The {0} argument was provided, but no schema \
files were found in the specified path(s).
ERR_SPLIT_LDIF_ERROR_LOADING_SCHEMA=An error occurred while attempting to \
read schema information from the specified schema path(s): {0}
ERR_SPLIT_LDIF_TRANSLATOR_CANNOT_GET_MD5=Unable to obtain an MD5 message \
digest generator: {0}
ERR_SPLIT_LDIF_RDN_HASH_TRANSLATOR_CANNOT_PARSE_DN=Unable to parse the entry \
DN: {0}
ERR_SPLIT_LDIF_ATTR_HASH_TRANSLATOR_CANNOT_PARSE_DN=Unable to parse the \
entry DN: {0}
ERR_SPLIT_LDIF_ATTR_HASH_TRANSLATOR_NON_FLAT_DIT=Unable to determine which \
set should hold an entry more than one level below split base DN ''{0}'' \
because the tool was configured to assume a flat DIT and therefore is not \
maintaining the cache needed to ensure that a subordinate entry is placed \
in the same set as its parent.
ERR_SPLIT_LDIF_FEWEST_ENTRIES_TRANSLATOR_CANNOT_PARSE_DN=Unable to parse the \
entry DN: {0}
ERR_SPLIT_LDIF_FEWEST_ENTRIES_TRANSLATOR_NON_FLAT_DIT=Unable to determine \
which set should hold an entry more than one level below split base DN \
''{0}'' because the tool was configured to assume a flat DIT and therefore \
is not maintaining the cache needed to ensure that a subordinate entry is \
placed in the same set as its parent.
ERR_SPLIT_LDIF_FILTER_TRANSLATOR_CANNOT_PARSE_DN=Unable to parse the entry \
DN: {0}
ERR_SPLIT_LDIF_FILTER_TRANSLATOR_NON_FLAT_DIT=Unable to determine which \
set should hold an entry more than one level below split base DN ''{0}'' \
because the tool was configured to assume a flat DIT and therefore is not \
maintaining the cache needed to ensure that a subordinate entry is placed \
in the same set as its parent.
INFO_TOOL_INTERRUPTED_BY_JVM_SHUTDOWN=Tool processing was interrupted by an \
unexpected JVM shutdown.
ERR_TOOL_LOGGER_ERROR_LOADING_PROPERTIES_FILE=An error occurred while \
trying to load the tool invocation logging properties from file ''{0}'': {1}
ERR_TOOL_LOGGER_CANNOT_PARSE_BOOLEAN_PROPERTY=Unable to parse value ''{0}'' \
of property ''{1}'' in tool invocation logging properties file ''{2}'' as \
a Boolean value.
ERR_TOOL_LOGGER_PATH_NOT_FILE=Value ''{0}'' for property ''{1}'' in tool \
invocation logging properties file ''{2}'' cannot be used as an invocation \
log file because the path references a directory rather than a file.
ERR_TOOL_LOGGER_PATH_PARENT_MISSING=Value ''{0}'' for property ''{1}'' in \
tool invocation logging properties file ''{2}'' cannot be used as an \
invocation log file because parent directory ''{3}'' either does not exist \
or is not a directory.
ERR_TOOL_LOGGER_NO_LOG_FILES=No invocation logging will be performed for \
command ''{0}'' because properties file ''{1}'' does not have a valid value \
for either the ''{2}'' or the ''{3}'' property.
ERR_TOOL_LOGGER_ERROR_WRITING_LOG_MESSAGE=An error occurred while trying to \
write a tool invocation log message to file ''{0}'': {1}
ERR_TOOL_LOGGER_ERROR_OPENING_LOG_FILE=An error occurred while trying to open \
log file ''{0}'' for writing an invocation log message: {1}
ERR_TOOL_LOGGER_UNABLE_TO_ACQUIRE_FILE_LOCK=Unable to acquire an exclusive \
lock on tool invocation log file ''{0}'' after {1,number,0} attempts.
ERR_TOOL_UTILS_ENCRYPTION_PW_FILE_MISSING=Encryption passphrase file ''{0}'' \
does not exist.
ERR_TOOL_UTILS_ENCRYPTION_PW_FILE_NOT_FILE=Encryption passphrase file ''{0}'' \
exists but is not a file.
ERR_TOOL_UTILS_ENCRYPTION_PW_FILE_EMPTY=Encryption passphrase file ''{0}'' is \
empty. The file must consist of exactly one line that is comprised \
entirely of the encryption passphrase.
ERR_TOOL_UTILS_ENCRYPTION_PW_FILE_MULTIPLE_LINES=Encryption passphrase file \
''{0}'' contains multiple lines. The file must consist of exactly one line \
that is comprised entirely of the encryption passphrase.
ERR_TOOL_UTILS_ENCRYPTION_PW_FILE_READ_ERROR=An error occurred while \
attempting to read the encryption passphrase from file ''{0}'': {1}
INFO_TOOL_UTILS_ENCRYPTION_PW_PROMPT=Enter the encryption passphrase:
ERR_TOOL_UTILS_ENCRYPTION_PW_EMPTY=ERROR: The encryption passphrase must not \
be empty.
INFO_TOOL_UTILS_ENCRYPTION_PW_CONFIRM=Confirm the encryption passphrase:
ERR_TOOL_UTILS_ENCRYPTION_PW_MISMATCH=ERROR: The passphrases do not match.
INFO_TOOL_UTILS_ENCRYPTED_LDIF_FILE_PW_PROMPT=LDIF file ''{0}'' is \
encrypted. Please enter the passphrase required to decrypt it:
ERR_TOOL_UTILS_ENCRYPTED_LDIF_FILE_WRONG_PW=The provided passphrase is \
incorrect.
ERR_TOOL_UTILS_ENCRYPTED_LDIF_FILE_CANNOT_DECRYPT=LDIF file ''{0}'' is \
encrypted, but an error occurred while attempting to decrypt it: {1}
© 2015 - 2025 Weber Informatics LLC | Privacy Policy