#[non_exhaustive]
pub enum CreateUserErrorKind {
DirectoryServiceAuthenticationFailedException(DirectoryServiceAuthenticationFailedException),
DirectoryUnavailableException(DirectoryUnavailableException),
InvalidParameterException(InvalidParameterException),
InvalidPasswordException(InvalidPasswordException),
NameAvailabilityException(NameAvailabilityException),
OrganizationNotFoundException(OrganizationNotFoundException),
OrganizationStateException(OrganizationStateException),
ReservedNameException(ReservedNameException),
UnsupportedOperationException(UnsupportedOperationException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the CreateUser
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
DirectoryServiceAuthenticationFailedException(DirectoryServiceAuthenticationFailedException)
The directory service doesn't recognize the credentials supplied by WorkMail.
The directory is unavailable. It might be located in another Region or deleted.
InvalidParameterException(InvalidParameterException)
One or more of the input parameters don't match the service's restrictions.
InvalidPasswordException(InvalidPasswordException)
The supplied password doesn't match the minimum security constraints, such as length or use of special characters.
NameAvailabilityException(NameAvailabilityException)
The user, group, or resource name isn't unique in WorkMail.
OrganizationNotFoundException(OrganizationNotFoundException)
An operation received a valid organization identifier that either doesn't belong or exist in the system.
OrganizationStateException(OrganizationStateException)
The organization must have a valid state to perform certain operations on the organization or its members.
ReservedNameException(ReservedNameException)
This user, group, or resource name is not allowed in WorkMail.
UnsupportedOperationException(UnsupportedOperationException)
You can't perform a write operation against a read-only directory.
Unhandled(Unhandled)
An unexpected error occurred (e.g., invalid JSON returned by the service or an unknown error code).
When logging an error from the SDK, it is recommended that you either wrap the error in
DisplayErrorContext
, use another
error reporter library that visits the error’s cause/source chain, or call
Error::source
for more details about the underlying cause.