From 625f051cca398870f1d96aa78a054efabf0d77ac Mon Sep 17 00:00:00 2001 From: Chris Ridd <chris.ridd@forgerock.com> Date: Mon, 15 Jul 2013 09:09:19 +0000 Subject: [PATCH] Remove unused messages --- opends/src/messages/messages/core.properties | 437 ------------------------------------------------------ 1 files changed, 0 insertions(+), 437 deletions(-) diff --git a/opends/src/messages/messages/core.properties b/opends/src/messages/messages/core.properties index 36d8e67..8c3a0e1 100644 --- a/opends/src/messages/messages/core.properties +++ b/opends/src/messages/messages/core.properties @@ -65,24 +65,6 @@ INFO_DISCONNECT_DUE_TO_IO_TIMEOUT_15=I/O Timeout INFO_DISCONNECT_BY_PLUGIN_16=Connection Closed by Plugin INFO_DISCONNECT_OTHER_17=Unknown Closure Reason -INFO_ERROR_CATEGORY_ACCESS_CONTROL_39=access-control -INFO_ERROR_CATEGORY_BACKEND_40=backend -INFO_ERROR_CATEGORY_CONFIG_41=config -INFO_ERROR_CATEGORY_CONNECTION_HANDLING_42=connection -INFO_ERROR_CATEGORY_CORE_SERVER_43=core -INFO_ERROR_CATEGORY_EXTENDED_OPERATION_45=extended-op -INFO_ERROR_CATEGORY_PLUGIN_46=plugin -INFO_ERROR_CATEGORY_REQUEST_HANDLING_47=request -INFO_ERROR_CATEGORY_SASL_MECHANISM_48=sasl -INFO_ERROR_CATEGORY_SHUTDOWN_49=shutdown -INFO_ERROR_CATEGORY_STARTUP_50=startup -INFO_ERROR_CATEGORY_SYNCHRONIZATION_51=sync -INFO_ERROR_SEVERITY_FATAL_ERROR_54=fatal-error -INFO_ERROR_SEVERITY_INFORMATIONAL_56=info -INFO_ERROR_SEVERITY_MILD_ERROR_57=mild-error -INFO_ERROR_SEVERITY_MILD_WARNING_58=mild-warning -INFO_ERROR_SEVERITY_SEVERE_ERROR_59=severe-error -INFO_ERROR_SEVERITY_SEVERE_WARNING_60=severe-warning INFO_RESULT_SUCCESS_63=Success INFO_RESULT_OPERATIONS_ERROR_64=Operations Error INFO_RESULT_PROTOCOL_ERROR_65=Protocol Error @@ -127,8 +109,6 @@ INFO_RESULT_TOO_LATE_103=Too Late INFO_RESULT_CANNOT_CANCEL_104=Cannot Cancel INFO_RESULT_OTHER_105=Other -MILD_WARN_UNKNOWN_ATTRIBUTE_USAGE_106=Unable to determine the attribute usage \ - type for attribute %s. The server will assume that it is user-defined INFO_CANCELED_BY_SHUTDOWN_107=Processing on this operation has been canceled \ because the Directory Server is shutting down MILD_ERR_UNCAUGHT_WORKER_THREAD_EXCEPTION_108=%s encountered an uncaught \ @@ -136,8 +116,6 @@ SEVERE_WARN_UNEXPECTED_WORKER_THREAD_EXIT_109=%s is unexpectedly exiting when \ the Directory Server is not in the process of shutting down. This likely \ indicates that the thread encountered an unexpected error -SEVERE_ERR_CANNOT_CREATE_WORKER_THREAD_110=An unexpected error occurred while \ - trying to create a worker thread: %s MILD_WARN_OP_REJECTED_BY_SHUTDOWN_111=The request to process this operation \ has been rejected because the Directory Server has already started its \ shutdown process @@ -172,7 +150,6 @@ FATAL_ERR_CANNOT_START_WHILE_RUNNING_123=The Directory Server may not be \ started while it is already running. Please stop the running instance \ before attempting to start it again -INFO_ERROR_CATEGORY_SCHEMA_124=schema MILD_ERR_ATTR_TYPE_NORMALIZE_NO_MR_125=Unable to normalize value %s for \ attribute type %s because no equality matching rule is defined for that \ attribute @@ -186,15 +163,11 @@ attempting to bootstrap the matching rule defined in class %s: %s SEVERE_ERR_CANNOT_BOOTSTRAP_SYNTAX_130=An error occurred while attempting to \ bootstrap the attribute syntax defined in class %s: %s -INFO_ERROR_SEVERITY_NOTICE_131=notice INFO_DIRECTORY_BOOTSTRAPPING_132=The Directory Server is beginning the \ configuration bootstrapping process -INFO_DIRECTORY_BOOTSTRAPPED_133=The Directory Server has completed the \ - configuration bootstrapping process NOTICE_DIRECTORY_SERVER_STARTING_134=%s (build %s, R%d) starting up NOTICE_DIRECTORY_SERVER_STARTED_135=The Directory Server has started \ successfully -INFO_ERROR_CATEGORY_EXTENSIONS_137=extensions FATAL_ERR_CANNOT_CREATE_MBEAN_SERVER_138=An error occurred while attempting \ to create the JMX MBean server that will be used for monitoring, \ notification, and configuration interaction within the Directory Server: %s @@ -309,17 +282,6 @@ MILD_ERR_RDN_ILLEGAL_CHARACTER_175=Unable to decode the provided string "%s" \ as a relative distinguished name because an illegal character %c was found at \ position %d, where either the end of the string or a '+' sign were expected -FATAL_ERR_CANNOT_CREATE_WORK_QUEUE_176=An error occurred while trying to \ - create the Directory Server work queue: %s. This is an unrecoverable error \ - and the startup process will not be able to continue -SEVERE_ERR_CANNOT_REGISTER_DUPLICATE_SUFFIX_180=The suffix "%s" is already \ - registered with the Directory Server with a backend of type %s -SEVERE_ERR_CANNOT_REGISTER_DUPLICATE_SUBSUFFIX_181=The suffix "%s" is already \ - registered with the Directory Server as a sub-suffix of the backend for \ - suffix "%s" -SEVERE_ERR_CANNOT_REGISTER_PRIVATE_SUFFIX_BELOW_USER_PARENT_182=The private \ - suffix "%s" is below a non-private suffix defined with a base DN of "%s". A \ - private sub-suffix may not exist below a non-private suffix SEVERE_ERR_CANNOT_GET_ROOT_DSE_CONFIG_ENTRY_183=An error occurred while \ trying to retrieve the root DSE configuration entry (cn=Root DSE,cn=config) \ from the Directory Server configuration: %s @@ -396,9 +358,6 @@ MILD_ERR_ENTRY_SCHEMA_PROHIBITED_ATTR_FOR_DCR_209=Entry %s violates the \ Directory Server schema configuration because it contains attribute %s which \ is prohibited by DIT content rule %s -MILD_ERR_ENTRY_SCHEMA_DISALLOWED_USER_ATTR_FOR_DCR_210=Entry %s violates the \ - Directory Server schema configuration because it includes attribute %s which \ - is not in the list of allowed or required attributes for DIT content rule %s MILD_ERR_ENTRY_SCHEMA_DISALLOWED_AUXILIARY_CLASS_211=Entry %s violates the \ Directory Server schema configuration because it includes auxiliary \ objectClass %s that is not allowed by DIT content rule %s @@ -438,12 +397,6 @@ with message ID %d because no information is available about that operation. \ This could mean that the target operation has already completed or was never \ requested -SEVERE_ERR_CANCELED_BY_PREPARSE_DISCONNECT_224=The operation was canceled \ - because the client connection was terminated by a pre-parse plugin -SEVERE_ERR_CANCELED_BY_PREOP_DISCONNECT_225=The operation was canceled \ - because the client connection was terminated by a pre-operation plugin -SEVERE_ERR_CANCELED_BY_POSTOP_DISCONNECT_226=The operation was canceled \ - because the client connection was terminated by a post-operation plugin SEVERE_ERR_COMPARE_CANNOT_LOCK_ENTRY_227=The Directory Server was unable to \ obtain a read lock on entry %s after multiple attempts. Processing on this \ operation cannot continue @@ -467,12 +420,6 @@ SEVERE_ERR_DELETE_CANNOT_LOCK_ENTRY_235=Entry %s cannot be removed because \ the server failed to obtain a write lock for this entry after multiple \ attempts -SEVERE_ERR_CANCELED_BY_SEARCH_ENTRY_DISCONNECT_236=The operation was canceled \ - because the client connection was terminated by a search result entry plugin \ - working on entry %s -SEVERE_ERR_CANCELED_BY_SEARCH_REF_DISCONNECT_237=The operation was canceled \ - because the client connection was terminated by a search result reference \ - plugin working on referral %s MILD_ERR_SEARCH_TIME_LIMIT_EXCEEDED_238=The maximum time limit of %d seconds \ for processing this search operation has expired MILD_ERR_SEARCH_SIZE_LIMIT_EXCEEDED_239=This search operation has sent the \ @@ -570,18 +517,12 @@ this connection has been disabled INFO_CONNHANDLER_CLOSED_BY_DELETE_274=The connection handler that accepted \ this connection has been removed from the server -MILD_ERR_ENTRY_SET_UNKNOWN_OC_275=Object class %s cannot be used in entry %s \ - because that class is not defined in the Directory Server schema MILD_ERR_ENTRY_ADD_UNKNOWN_OC_276=Object class %s cannot be added to entry %s \ because that class is not defined in the Directory Server schema MILD_ERR_ENTRY_ADD_DUPLICATE_OC_277=Object class %s is already present in \ entry %s and cannot be added a second time -MILD_ERR_BIND_OPERATION_UNKNOWN_STORAGE_SCHEME_278=Password with unknown \ - storage scheme %s included in user entry will be ignored MILD_ERR_BIND_OPERATION_WRONG_PASSWORD_279=The password provided by the user \ did not match any password(s) stored in the user's entry -MILD_ERR_BIND_OPERATION_PASSWORD_VALIDATION_EXCEPTION_280=An unexpected error \ - occurred while attempting to validate the provided password: %s INFO_DSCORE_DESCRIPTION_CONFIG_CLASS_281=Fully-qualified name \ of the Java class to use as the Directory Server configuration handler INFO_DSCORE_DESCRIPTION_CONFIG_FILE_282=Path to the file \ @@ -590,7 +531,6 @@ INFO_DSCORE_DESCRIPTION_FULLVERSION_284=Display extended Directory Server \ version information INFO_DSCORE_DESCRIPTION_SYSINFO_285=Display general system information -INFO_DSCORE_DESCRIPTION_DUMPMESSAGES_286=Dump a list of all defined messages INFO_DSCORE_DESCRIPTION_USAGE_287=Display this usage information FATAL_ERR_DSCORE_CANNOT_INITIALIZE_ARGS_288=An error occurred while \ attempting to initialize the command-line arguments: %s @@ -715,7 +655,6 @@ FATAL_ERR_CANNOT_ACQUIRE_EXCLUSIVE_SERVER_LOCK_343=The Directory Server could \ not acquire an exclusive lock on file %s: %s. This generally means that \ another instance of this server is already running -INFO_ERROR_CATEGORY_TASK_345=task MILD_ERR_MODIFY_ATTR_IS_NO_USER_MOD_346=Entry %s cannot be modified because \ the modification attempted to update attribute %s which is defined as \ NO-USER-MODIFICATION in the server schema @@ -730,25 +669,6 @@ because the new RDN includes attribute %s which is defined as \ NO-USER-MODIFICATION in the server schema, and the target value for that \ attribute is not already included in the entry -MILD_ERR_MODDN_PREOP_INCREMENT_NO_ATTR_350=The modify DN operation for entry \ - %s cannot be performed because a pre-operation plugin attempted to increment \ - attribute %s but that attribute does not exist in the target entry -MILD_ERR_MODDN_PREOP_INCREMENT_MULTIPLE_VALUES_351=The modify DN operation \ - for entry %s cannot be performed because a pre-operation plugin attempted to \ - increment attribute %s but that attribute has multiple values in the target \ - entry -MILD_ERR_MODDN_PREOP_INCREMENT_VALUE_NOT_INTEGER_352=The modify DN operation \ - for entry %s cannot be performed because a pre-operation plugin attempted to \ - increment attribute %s but the value of that attribute is not an integer -MILD_ERR_MODDN_PREOP_INCREMENT_NO_AMOUNT_353=The modify DN operation for \ - entry %s cannot be performed because a pre-operation plugin attempted to \ - increment attribute %s but no increment amount was provided -MILD_ERR_MODDN_PREOP_INCREMENT_MULTIPLE_AMOUNTS_354=The modify DN operation \ - for entry %s cannot be performed because a pre-operation plugin attempted to \ - increment attribute %s but multiple increment amount values were provided -MILD_ERR_MODDN_PREOP_INCREMENT_AMOUNT_NOT_INTEGER_355=The modify DN operation \ - for entry %s cannot be performed because a pre-operation plugin attempted to \ - increment attribute %s but the increment amount value was not an integer MILD_ERR_MODDN_PREOP_VIOLATES_SCHEMA_356=The modify DN operation for entry %s \ cannot be performed because a pre-operation plugin modified the entry in a \ way that caused it to violate the server schema: %s @@ -762,14 +682,6 @@ MILD_ERR_MODIFY_UNSUPPORTED_CRITICAL_CONTROL_359=Entry %s cannot be modified \ because the request contained a critical control with OID %s that is not \ supported by the Directory Server for this type of operation -MILD_ERR_DELETE_CANNOT_GET_ENTRY_FOR_ASSERTION_360=Entry %s cannot be removed \ - because the delete request contains an LDAP assertion control and an error \ - occurred while trying to retrieve the target entry to compare it against the \ - associated filter: %s -MILD_ERR_DELETE_NO_SUCH_ENTRY_FOR_ASSERTION_361=Entry %s cannot be removed \ - because it was determined that the target entry does not exist while \ - attempting to process it against the LDAP assertion control contained in the \ - request MILD_ERR_DELETE_ASSERTION_FAILED_362=Entry %s cannot be removed because the \ request contained an LDAP assertion control and the associated filter did not \ match the contents of the entry @@ -840,9 +752,6 @@ INFO_MODDN_NOOP_382=The modify DN operation was not actually performed in the \ Directory Server backend because the LDAP no-op control was present in the \ request -MILD_ERR_DELETE_PREREAD_NO_ENTRY_383=Entry %s cannot be removed because it \ - was determined that the target entry does not exist while attempting to \ - process it against the LDAP pre-read request control INFO_RESULT_AUTHORIZATION_DENIED_384=Authorization Denied SEVERE_ERR_ADD_MISSING_RDN_ATTRIBUTE_385=Entry %s cannot be added because it \ is missing attribute %s that is contained in the entry's RDN. All attributes \ @@ -850,27 +759,15 @@ SEVERE_ERR_ADD_ERROR_NOTIFYING_CHANGE_LISTENER_386=An unexpected error \ occurred while notifying a change notification listener of an add operation: \ %s -SEVERE_ERR_ADD_ERROR_NOTIFYING_PERSISTENT_SEARCH_387=An unexpected error \ - occurred while notifying persistent search %s of an add operation: %s. The \ - persistent search has been terminated SEVERE_ERR_DELETE_ERROR_NOTIFYING_CHANGE_LISTENER_388=An unexpected error \ occurred while notifying a change notification listener of a delete \ operation: %s -SEVERE_ERR_DELETE_ERROR_NOTIFYING_PERSISTENT_SEARCH_389=An unexpected error \ - occurred while notifying persistent search %s of a delete operation: %s. \ - The persistent search has been terminated SEVERE_ERR_MODIFY_ERROR_NOTIFYING_CHANGE_LISTENER_390=An unexpected error \ occurred while notifying a change notification listener of a modify \ operation: %s -SEVERE_ERR_MODIFY_ERROR_NOTIFYING_PERSISTENT_SEARCH_391=An unexpected error \ - occurred while notifying persistent search %s of a modify operation: %s. \ - The persistent search has been terminated SEVERE_ERR_MODDN_ERROR_NOTIFYING_CHANGE_LISTENER_392=An unexpected error \ occurred while notifying a change notification listener of a modify DN \ operation: %s -SEVERE_ERR_MODDN_ERROR_NOTIFYING_PERSISTENT_SEARCH_393=An unexpected error \ - occurred while notifying persistent search %s of a modify DN operation: %s. \ - The persistent search has been terminated SEVERE_ERR_BIND_UNSUPPORTED_CRITICAL_CONTROL_394=Unable to process the bind \ request because it contained a control with OID %s that was marked critical \ but this control is not supported for the bind operation @@ -944,17 +841,6 @@ SEVERE_ERR_BIND_DN_BUT_NO_PASSWORD_421=Unable to process the simple bind \ request because it contained a bind DN but no password, which is forbidden by \ the server configuration -SEVERE_ERR_PWPOLICY_NO_PASSWORD_ATTRIBUTE_422=The password policy \ - configuration entry "%s" does not contain a value for attribute \ - ds-cfg-password-attribute, which specifies the attribute to hold user \ - passwords -SEVERE_ERR_PWPOLICY_NO_DEFAULT_STORAGE_SCHEMES_423=The password policy \ - configuration entry "%s" does not contain any values for attribute \ - ds-cfg-default-password-storage-scheme, which specifies the set of default \ - password storage schemes -INFO_PWPOLICY_DESCRIPTION_PW_ATTR_424=Attribute type used to \ - hold user passwords. This attribute type must be defined in the server \ - schema. Changes to this configuration attribute will take effect immediately SEVERE_ERR_PWPOLICY_UNDEFINED_PASSWORD_ATTRIBUTE_425=The password policy \ definition contained in configuration entry "%s" is invalid because the \ specified password attribute "%s" is not defined in the server schema @@ -964,303 +850,20 @@ attribute must have a syntax OID of either 1.3.6.1.4.1.26027.1.3.1 (for the \ user password syntax) or 1.3.6.1.4.1.4203.1.1.2 (for the authentication \ password syntax) -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_PASSWORD_ATTRIBUTE_427=An error occurred \ - while attempting to determine the value of attribute \ - ds-cfg-password-attribute in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_DEFAULT_STORAGE_SCHEMES_428=Password \ - storage scheme (or set of schemes) that will be used to encode clear-text \ - passwords. If multiple default storage schemes are defined for a password \ - policy, then the same password will be encoded using all of those schemes. \ - Changes to this configuration attribute will take effect immediately -SEVERE_ERR_PWPOLICY_NO_SUCH_DEFAULT_SCHEME_429=The password policy definition \ - contained in configuration entry "%s" is invalid because it references a \ - default password storage scheme "%s" that is not defined in the server \ - configuration -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_DEFAULT_STORAGE_SCHEMES_430=An error \ - occurred while attempting to determine the values for attribute \ - ds-cfg-default-password-storage-scheme in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_DEPRECATED_STORAGE_SCHEMES_431=Password storage \ - scheme (or set of schemes) that should be considered \ - deprecated. If an authenticating user has a password encoded with one of \ - these schemes, those passwords will be removed and replaced with passwords \ - encoded using the default schemes. Changes to this configuration attribute \ - will take effect immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_DEPRECATED_STORAGE_SCHEMES_432=An error \ - occurred while attempting to determine the values for attribute \ - ds-cfg-deprecated-password-storage-scheme in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_PASSWORD_VALIDATORS_433=DN(s) of the \ - password validator(s) that should be used with the associated password \ - storage scheme. Changes to this configuration attribute will take effect \ - immediately -SEVERE_ERR_PWPOLICY_NO_SUCH_VALIDATOR_434=The password policy definition \ - contained in configuration entry "%s" is invalid because it references a \ - password validator "%s" that is not defined in the server configuration -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_PASSWORD_VALIDATORS_435=An error \ - occurred while attempting to determine the values for attribute \ - ds-cfg-password-validator in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_NOTIFICATION_HANDLERS_436=DN(s) of \ - the account status notification handler(s) that should be used with the \ - associated password storage scheme. Changes to this configuration attribute \ - will take effect immediately -SEVERE_ERR_PWPOLICY_NO_SUCH_NOTIFICATION_HANDLER_437=The password policy \ - definition contained in configuration entry "%s" is invalid because it \ - references account status notification handler "%s" that is not defined in \ - the server configuration -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_NOTIFICATION_HANDLERS_438=An error \ - occurred while attempting to determine the values for attribute \ - ds-cfg-account-status-notification-handler in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_ALLOW_USER_PW_CHANGES_439=Indicates whether users \ - will be allowed to change their own passwords. This check is made in \ - addition to access control evaluation, and therefore both must allow the \ - password change for it to occur. Changes to this configuration attribute \ - will take effect immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_ALLOW_USER_PW_CHANGES_440=An error \ - occurred while attempting to determine the value for attribute \ - ds-cfg-allow-user-password-changes in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_REQUIRE_CURRENT_PW_441=Indicates whether user \ - password changes will be required to use the password modify extended \ - operation and include the user's current password before the change will be \ - allowed. Changes to this configuration attribute will take effect \ - immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_REQUIRE_CURRENT_PW_442=An error occurred \ - while attempting to determine the value for attribute \ - ds-cfg-allow-user-password-changes in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_FORCE_CHANGE_ON_RESET_443=Indicates whether users \ - will be forced to change their passwords if they are reset by an \ - administrator. For this purpose, anyone with permission to change a given \ - user's password other than that user will be considered an administrator. \ - Changes to this configuration attribute will take effect immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_FORCE_CHANGE_ON_RESET_444=An error \ - occurred while attempting to determine the value for attribute \ - ds-cfg-force-change-on-reset in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_SKIP_ADMIN_VALIDATION_445=Indicates whether \ - passwords set by administrators (in add, modify, or password modify \ - operations) will be allowed to bypass the password validation process that \ - will be required for user password changes. Changes to this configuration \ - attribute will take effect immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_SKIP_ADMIN_VALIDATION_446=An error \ - occurred while attempting to determine the value for attribute \ - ds-cfg-skip-validation-for-administrators in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_PASSWORD_GENERATOR_447=DN of the \ - configuration entry that references the password generator for use with the \ - associated password policy. This will be used in conjunction with the \ - password modify extended operation to generate a new password for a user when \ - none was provided in the request. Changes to this configuration attribute \ - will take effect immediately -SEVERE_ERR_PWPOLICY_NO_SUCH_GENERATOR_448=The password policy definition \ - contained in configuration entry "%s" is invalid because it references \ - password generator "%s" that is not defined in the server configuration -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_PASSWORD_GENERATOR_449=An error occurred \ - while attempting to determine the value for attribute \ - ds-cfg-password-generator in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_REQUIRE_SECURE_AUTH_450=Indicates whether users \ - with the associated password policy will be required to authenticate in a \ - secure manner. This could mean either using a secure communication channel \ - between the client and the server, or using a SASL mechanism that does not \ - expose the credentials. Changes to this configuration attribute will take \ - effect immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_REQUIRE_SECURE_AUTH_451=An error \ - occurred while attempting to determine the value for attribute \ - ds-cfg-require-secure-authentication in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_REQUIRE_SECURE_CHANGES_452=Indicates whether users \ - with the associated password policy will be required to change their password \ - in a secure manner that does not expose the credentials. Changes to this \ - configuration attribute will take effect immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_REQUIRE_SECURE_CHANGES_453=An error \ - occurred while attempting to determine the value for attribute \ - ds-cfg-require-secure-password-changes in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_ALLOW_PREENCODED_454=Indicates whether users will \ - be allowed to change their passwords by providing a pre-encoded value. This \ - can cause a security risk because the clear-text version of the password is \ - not known and therefore validation checks cannot be applied to it. Changes \ - to this configuration attribute will take effect immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_ALLOW_PREENCODED_455=An error occurred \ - while attempting to determine the value for attribute \ - ds-cfg-allow-pre-encoded-passwords in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_MIN_AGE_456=Minimum length of time \ - that must pass after a password change before the user will be allowed to \ - change the password again. The value of this attribute should be an integer \ - followed by a unit of seconds, minutes, hours, days, or weeks. This setting \ - can be used to prevent users from changing their passwords repeatedly over a \ - short period of time to flush and old password from the history so that it \ - may be re-used. Changes to this configuration attribute will take effect \ - immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_MIN_AGE_457=An error occurred while \ - attempting to determine the value for attribute ds-cfg-min-password-age \ - in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_MAX_AGE_458=Maximum length of time \ - that a user may continue using the same password before it must be changed \ - (i.e., the password expiration interval). The value of this attribute should \ - be an integer followed by a unit of seconds, minutes, hours, days, or weeks. \ - A value of 0 seconds will disable password expiration. Changes to this \ - configuration attribute will take effect immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_MAX_AGE_459=An error occurred while \ - attempting to determine the value for attribute ds-cfg-max-password-age \ - in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_MAX_RESET_AGE_460=Maximum length of \ - time that users have to change passwords after they have been reset by an \ - administrator before they become locked. The value of this attribute should \ - be an integer followed by a unit of seconds, minutes, hours, days, or weeks. \ - A value of 0 seconds will disable this feature. Changes to this \ - configuration attribute will take effect immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_MAX_RESET_AGE_461=An error occurred \ - while attempting to determine the value for attribute \ - ds-cfg-max-password-reset-age in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_WARNING_INTERVAL_462=Maximum length \ - of time before a user's password actually expires that the server will begin \ - to include warning notifications in bind responses for that user. The value \ - of this attribute should be an integer followed by a unit of seconds, \ - minutes, hours, days, or weeks. A value of 0 seconds will disable the \ - warning interval. Changes to this configuration attribute will take effect \ - immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_WARNING_INTERVAL_463=An error occurred \ - while attempting to determine the value for attribute \ - ds-cfg-password-expiration-warning-interval in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_EXPIRE_WITHOUT_WARNING_464=Indicates whether the \ - Directory Server should allow a user's password to expire even if that user \ - has never seen an expiration warning notification. If this setting is \ - enabled, then accounts will always be expired when the expiration time \ - arrives. If it is disabled, then the user will always receive at least one \ - warning notification, and the password expiration will be set to the warning \ - time plus the warning interval. Changes to this configuration attribute will \ - take effect immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_EXPIRE_WITHOUT_WARNING_465=An error \ - occurred while attempting to determine the value for attribute \ - ds-cfg-expire-passwords-without-warning in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_ALLOW_EXPIRED_CHANGES_466=Indicates whether a user \ - whose password is expired will still be allowed to change that password using \ - the password modify extended operation. Changes to this configuration \ - attribute will take effect immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_ALLOW_EXPIRED_CHANGES_467=An error \ - occurred while attempting to determine the value for attribute \ - ds-cfg-allow-expired-password-changes in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_GRACE_LOGIN_COUNT_468=Number of grace \ - logins that a user will be allowed after the account has expired to allow \ - that user to choose a new password. A value of 0 indicates that no grace \ - logins will be allowed. Changes to this configuration attribute will take \ - effect immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_GRACE_LOGIN_COUNT_469=An error occurred \ - while attempting to determine the value for attribute \ - ds-cfg-grace-login-count in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_LOCKOUT_FAILURE_COUNT_470=Maximum \ - number of authentication failures that a user should be allowed before the \ - account is locked out. A value of 0 indicates that accounts should never be \ - locked out due to failed attempts. changes to this configuration attribute \ - will take effect immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_LOCKOUT_FAILURE_COUNT_471=An error \ - occurred while attempting to determine the value for attribute \ - ds-cfg-lockout-failure-count in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_LOCKOUT_DURATION_472=Length of time \ - that an account should be locked after too many authentication failures. The \ - value of this attribute should be an integer followed by a unit of seconds, \ - minutes, hours, days, or weeks. A value of 0 seconds indicates that the \ - account should remain locked until an administrator resets the password. \ - Changes to this configuration attribute will take effect immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_LOCKOUT_DURATION_473=An error occurred \ - while attempting to determine the value for attribute ds-cfg-lockout-duration \ - in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_FAILURE_EXPIRATION_474=Length of time \ - that should pass before an authentication failure is no longer counted \ - against a user for the purposes of account lockout. The value of this \ - attribute should be an integer followed by a unit of seconds, minutes, hours, \ - days, or weeks. A value of 0 seconds indicates that the authentication \ - failures should never expire. The failure count will always be cleared upon \ - a successful authentication. Changes to this configuration attribute will \ - take effect immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_FAILURE_EXPIRATION_475=An error occurred \ - while attempting to determine the value for attribute \ - ds-cfg-lockout-failure-expiration-interval in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_REQUIRE_CHANGE_BY_TIME_476=Time by \ - which all users with the associated password policy must change their \ - passwords. The value should be expressed in a generalized time format. If \ - this time is equal to the current time or is in the past, then all users will \ - be required to change their passwords immediately. The behavior of the \ - server in this mode will be identical to the behavior observed when users are \ - forced to change their passwords after an administrative reset. Changes to \ - this configuration attribute will take effect immediately SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_REQUIRE_CHANGE_BY_TIME_477=An error \ occurred while attempting to determine the value for attribute \ ds-cfg-require-change-by-time in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_LAST_LOGIN_TIME_ATTR_478=Name or OID \ - of the attribute type that should be used to hold the last login time for \ - users with the associated password policy. This attribute type must be \ - defined in the Directory Server schema and must either be defined as an \ - operational attribute or must be allowed by the set of object classes for all \ - users with the associated password policy. Changes to this configuration \ - attribute will take effect immediately -SEVERE_ERR_PWPOLICY_UNDEFINED_LAST_LOGIN_TIME_ATTRIBUTE_479=The password \ - policy definition contained in configuration entry "%s" is invalid because \ - the specified last login time attribute "%s" is not defined in the server \ - schema -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_LAST_LOGIN_TIME_ATTR_480=An error \ - occurred while attempting to determine the value for attribute \ - ds-cfg-last-login-time-attribute in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_LAST_LOGIN_TIME_FORMAT_481=Format \ - string that should be used to generate the last login time value for users \ - with the associated password policy. This format string should conform to \ - the syntax described in the API documentation for the \ - <CODE>java.text.SimpleDateFormat</CODE> class. Changes to this configuration \ - attribute will take effect immediately SEVERE_ERR_PWPOLICY_INVALID_LAST_LOGIN_TIME_FORMAT_482=The password policy \ definition contained in configuration entry "%s" is invalid because the \ specified last login time format "%s" is not a valid format string The last \ login time format string should conform to the syntax described in the API \ documentation for the <CODE>java.text.SimpleDateFormat</CODE> class -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_LAST_LOGIN_TIME_FORMAT_483=An error \ - occurred while attempting to determine the value for attribute \ - ds-cfg-last-login-time-format in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_PREVIOUS_LAST_LOGIN_TIME_FORMAT_484=Format \ - string(s) that may have been used with the last login time at any \ - point in the past for users associated with the password policy. These \ - values are used to make it possible to parse previous values, but will not be \ - used to set new values. These format strings should conform to the syntax \ - described in the API documentation for the \ - <CODE>java.text.SimpleDateFormat</CODE> class. Changes to this configuration \ - attribute will take effect immediately SEVERE_ERR_PWPOLICY_INVALID_PREVIOUS_LAST_LOGIN_TIME_FORMAT_485=The password \ policy definition contained in configuration entry "%s" is invalid because \ the specified previous last login time format "%s" is not a valid format \ string The previous last login time format strings should conform to the \ syntax described in the API documentation for the \ <CODE>java.text.SimpleDateFormat</CODE> class -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_PREVIOUS_LAST_LOGIN_TIME_FORMAT_486=An \ - error occurred while attempting to determine the values for attribute \ - ds-cfg-previous-last-login-time-format in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_IDLE_LOCKOUT_INTERVAL_487=Maximum \ - length of time that an account may remain idle (i.e., the associated user \ - does not authenticate to the server) before that user is locked out. The \ - value of this attribute should be an integer followed by a unit of seconds, \ - minutes, hours, days, or weeks. A value of 0 seconds indicates that idle \ - accounts should not automatically be locked out. This feature will only be \ - available if the last login time is maintained. Changes to this \ - configuration attribute will take effect immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_IDLE_LOCKOUT_INTERVAL_488=An error \ - occurred while attempting to determine the value for attribute \ - ds-cfg-idle-lockout-interval in configuration entry %s: %s -INFO_PWPOLICY_UPDATED_POLICY_489=The password policy defined in configuration \ - entry %s has been successfully updated -MILD_ERR_ADD_INVALID_PWPOLICY_DN_SYNTAX_490=Entry "%s" cannot be added \ - because it contains an invalid password policy subentry DN: %s -MILD_ERR_ADD_NO_SUCH_PWPOLICY_491=Entry "%s" cannot be added because it \ - references password policy subentry %s that does not exist or does not \ - contain a valid password policy subentry definition -INFO_PWPOLICY_DESCRIPTION_FORCE_CHANGE_ON_ADD_492=Indicates whether users \ - will be forced to change their passwords upon first authenticating to the \ - Directory Server after their account has been created. Changes to this \ - configuration attribute will take effect immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_FORCE_CHANGE_ON_ADD_493=An error \ - occurred while attempting to determine the value for attribute \ - ds-cfg-force-change-on-add in configuration entry %s: %s -INFO_PWPOLICY_DESCRIPTION_ALLOW_MULTIPLE_PW_VALUES_494=Indicates whether user \ - entries will be allowed to have multiple distinct values for the password \ - attribute. This is potentially dangerous because many mechanisms used to \ - change the password do not work well with such a configuration. If multiple \ - password values are allowed, then any of them may be used to authenticate, \ - and they will all be subject to the same policy constraints. Changes to this \ - configuration attribute will take effect immediately -SEVERE_ERR_PWPOLICY_CANNOT_DETERMINE_ALLOW_MULTIPLE_PW_VALUES_495=An error \ - occurred while attempting to determine the value for attribute \ - ds-cfg-allow-multiple-password-values in configuration entry %s: %s MILD_ERR_PWPOLICY_ATTRIBUTE_OPTIONS_NOT_ALLOWED_496=Attribute options are not \ allowed for the password attribute %s MILD_ERR_PWPOLICY_MULTIPLE_PW_VALUES_NOT_ALLOWED_497=Only a single value may \ @@ -1327,21 +930,6 @@ MILD_ERR_BIND_OPERATION_INSECURE_SASL_BIND_523=Rejecting a SASL %s bind \ request for user %s because the password policy requires secure \ authentication -SEVERE_ERR_WORKQ_CANNOT_PARSE_DN_524=An error occurred while attempting to \ - parse string %s as the DN of the work queue configuration entry: %s -SEVERE_ERR_WORKQ_NO_CONFIG_525=Work queue configuration entry %s does not \ - exist in the server configuration -INFO_WORKQ_DESCRIPTION_CLASS_526=Fully-qualified name of the \ - Java class that provides the core work queue logic for the Directory Server. \ - Changes to this configuration attribute require that the server be restarted \ - for the change to take effect -SEVERE_ERR_WORKQ_NO_CLASS_ATTR_527=Configuration entry %s does not contain \ - required attribute %s that specifies the fully-qualified class name for the \ - work queue implementation -SEVERE_ERR_WORKQ_CANNOT_LOAD_528=An error occurred while trying to load class \ - %s to use as the Directory Server work queue implementation: %s -SEVERE_ERR_WORKQ_CANNOT_INSTANTIATE_529=An error occurred while trying to \ - create an instance of class %s to use as the Directory Server work queue: %s SEVERE_ERR_CANNOT_REGISTER_DUPLICATE_ALTERNATE_ROOT_BIND_DN_530=The alternate \ root bind DN "%s" is already registered with the Directory Server for actual \ root entry DN "%s" @@ -1363,8 +951,6 @@ %s attempted on password attribute %s MILD_ERR_MODIFY_NO_EXISTING_VALUES_539=The user entry does not have any \ existing passwords to remove -MILD_ERR_MODIFY_CANNOT_DECODE_PW_540=An error occurred while attempting to \ - decode an existing user password: %s MILD_ERR_MODIFY_INVALID_PASSWORD_541=The provided user password does not \ match any password in the user's entry MILD_ERR_MODIFY_PW_CHANGE_REQUIRES_CURRENT_PW_542=The password policy \ @@ -1376,7 +962,6 @@ rejected by a password validator: %s MILD_ERR_MODIFY_MUST_CHANGE_PASSWORD_545=%s must change their password before \ it will be allowed to perform any other operations -INFO_ERROR_CATEGORY_PASSWORD_POLICY_546=pw-policy MILD_WARN_BIND_PASSWORD_EXPIRING_547=The user password is about to expire \ (time to expiration: %s) MILD_ERR_BIND_ACCOUNT_TEMPORARILY_LOCKED_548=The account has been locked as a \ @@ -1384,8 +969,6 @@ MILD_ERR_BIND_ACCOUNT_PERMANENTLY_LOCKED_549=The account has been locked as a \ result of too many failed authentication attempts. It may only be unlocked \ by an administrator -MILD_ERR_MODIFY_INVALID_DISABLED_VALUE_550=Invalid value provided for \ - operational attribute %s: %s INFO_MODIFY_PASSWORD_CHANGED_551=The user password has been changed INFO_MODIFY_PASSWORD_RESET_552=The user password has been administratively \ reset @@ -1412,8 +995,6 @@ supported for the objectClass attribute MILD_ERR_ENTRY_UNKNOWN_MODIFICATION_TYPE_562=Unknown modification type %s \ requested -MILD_ERR_ENTRY_INCREMENT_MULTIPLE_VALUES_563=Unable to increment the value of \ - attribute %s because there are multiple values for that attribute MILD_ERR_ENTRY_INCREMENT_INVALID_VALUE_COUNT_564=Unable to increment the \ value of attribute %s because the provided modification did not have exactly \ one value to use as the increment @@ -1521,18 +1102,6 @@ MILD_ERR_SEARCH_FILTER_NOT_EXACTLY_ONE_602=The provided search filter "%s" \ could not be decoded because the NOT filter between positions %d and %d did \ not contain exactly one filter component -MILD_ERR_SORTKEY_INVALID_ORDER_INDICATOR_603=The provided sort key value %s \ - is invalid because it does not start with either '+' (to indicate sorting in \ - ascending order) or '-' (to indicate sorting in descending order) -MILD_ERR_SORTKEY_UNDEFINED_TYPE_604=The provided sort key value %s is invalid \ - because it references undefined attribute type %s -MILD_ERR_SORTKEY_NO_ORDERING_RULE_605=The provided sort key value %s is \ - invalid because attribute type %s does not have a default ordering matching \ - rule and no specific rule was provided -MILD_ERR_SORTKEY_UNDEFINED_ORDERING_RULE_606=The provided sort key value %s \ - is invalid because it references undefined ordering matching rule %s -MILD_ERR_SORTORDER_DECODE_NO_KEYS_607=The provided sort order string "%s" is \ - invalid because it does not contain any sort keys INFO_RESULT_SORT_CONTROL_MISSING_608=Sort Control Missing INFO_RESULT_OFFSET_RANGE_ERROR_609=Offset Range Error INFO_RESULT_VIRTUAL_LIST_VIEW_ERROR_610=Virtual List View Error @@ -1541,9 +1110,6 @@ SEVERE_ERR_HOST_PORT_ALREADY_SPECIFIED_612=The connection handler %s is \ trying to use the listener %s which is already in use by another connection \ handler -SEVERE_ERR_HOST_PORT_CANNOT_BE_USED_613=The server cannot use the listener %s \ - of connection handler %s because it is already being used by another process \ - or because it does not have the rights to use it SEVERE_ERR_NOT_AVAILABLE_CONNECTION_HANDLERS_614=No enabled connection \ handler available SEVERE_ERR_ERROR_STARTING_CONNECTION_HANDLERS_615=Could not start connection \ @@ -1660,9 +1226,6 @@ SEVERE_ERR_PWPOLICY_SCHEME_DOESNT_SUPPORT_AUTH_657=The password storage \ scheme defined in configuration entry %s does not support the auth password \ syntax, which is used by password attribute %s -SEVERE_ERR_PWPOLICY_NO_SUCH_DEPRECATED_SCHEME_658=Password policy \ - configuration entry %s references deprecated password storage scheme DN %s \ - which is not available for use in the server SEVERE_ERR_PWPOLICY_DEPRECATED_SCHEME_NOT_AUTH_659=Password policy \ configuration entry %s references deprecated password storage scheme DN %s \ which does not support the auth password syntax -- Gitblit v1.10.0