Tenants API

The Id to use for the new Tenant. If not specified a secure random UUID will be generated.

The Id of the IP Access Control List limiting access to all applications in this tenant.

Note: To use IP ACLs, you'll need an Enterprise plan.

The default base URL used when rendering links in templates for this Tenant. This value is used when application.baseURL is not defined.

The type of CAPTCHA method to use. This field is required when tenant.captchaConfiguration.enabled is set to true. The possible values are:

• GoogleRecaptchaV2 - use Google reCAPTCHA v2
• GoogleRecaptchaV3 - use Google reCAPTCHA v3
• HCaptcha - use HCaptcha
• HCaptchaEnterprise - use HCaptcha Enterprise - v25

Note: To use CAPTCHA, you'll need an Enterprise plan.

Whether CAPTCHA configuration is enabled.

Note: To use CAPTCHA, you'll need an Enterprise plan.

The secret key for this CAPTCHA method. This field is required when tenant.captchaConfiguration.enabled is set to true.

Note: To use CAPTCHA, you'll need an Enterprise plan.

The site key for this CAPTCHA method. This field is required when tenant.captchaConfiguration.enabled is set to true.

Note: To use CAPTCHA, you'll need an Enterprise plan.

The numeric threshold which separates a passing score from a failing one. This value only applies if using either the Google v3 or HCaptcha Enterprise method, otherwise this value is ignored.

The value must be between 0.0 and 1.0. Values outside of that range will result in an error.

Note: To use CAPTCHA, you'll need an Enterprise plan.

Whether or not FusionAuth should use custom signal configuration calculating client risk. The score is available to MFA policies, and the MFA requirement lambda. Disabled signals are excluded from all risk calculations. Disabling all signals sets the risk score to HIGH.

Checks whether the client's IP address appears on a blocklist.

Detects bot interactions with the browser window.

Checks if the user has not logged in for a long period of time.

Checks if the user's password has not been changed for a long period of time.

Tracks geographic locations for login attempts. Flags a login as high risk if it occurs sooner than it would take to physically travel from the previous location to the current location.

Checks if the user's login ID has been changed recently.

Checks if the user's password has been changed recently.

Checks whether the client's user agent has been flagged as suspicious.

Checks whether the request originates from an unrecognized device.

Checks if the request originates from a device that is not in the user's trusted device list.

A list of Connector policies. Users will be authenticated against Connectors in order. Each Connector can be included in this list at most once and must exist.

The identifier of the Connector to which this policy refers.

An list of email domains to which this connector should apply.

A value of ["*"] indicates this connector applies to all users.

If true, the user's data will be migrated to FusionAuth at first successful authentication; subsequent authentications will occur against the FusionAuth datastore. If false, the Connector's source will be treated as authoritative.

Prior to version 1.28.0 this value was required.

An object that can hold any information about the Tenant that should be persisted.

The additional SMTP headers to be added to each outgoing email. Each SMTP header consists of a name and a value.

Determines if debug should be enabled to create an event log to assist in debugging SMTP errors.

The default email address that emails will be sent from when a from address is not provided on an individual email template. This is the address part email address (i.e. Jared Dunn jared@piedpiper.com).

The default From Name used in sending emails when a from name is not provided on an individual email template. This is the display name part of the email address ( i.e. Jared Dunn jared@piedpiper.com).

The Id of the Email Template used to send emails to users when their email address is updated.

The Id of the Email Template used to notify a user that their email address has been verified.

The Id of the Email Template that is used when a user is sent a forgot password email.

The host name of the SMTP server that FusionAuth will use.

Prior to version 1.28.0 this value was required.

When set to true, this allows email to be verified as a result of completing a similar email based workflow such as change password. When set to false, the user must explicitly complete the email verification workflow even if the user has already completed a similar email workflow such as change password.

The Id of the Email Template used to send emails to users when another user attempts to create an account with their login Id.

The Id of the Email Template used to send emails to users when another user attempts to update an existing account to use their login Id.

The Id of the Email Template used to send emails to users when they log in on a new device.

The Id of the Email Template used to send emails to users when a suspicious login occurs.

An optional password FusionAuth will use to authenticate with the SMTP server.

The Id of the Passwordless Email Template, sent to users when they start a passwordless login.

The Id of the Email Template used to send emails to users when they have completed a 'forgot password' workflow and their password has been reset.

The Id of the Email Template used to send emails to users when their password has been updated.

The port of the SMTP server that FusionAuth will use.

Prior to version 1.28.0 this value was required.

Custom SMTP configuration properties that may be necessary in some cases. This can contain any Java mail property. It will override anything FusionAuth sets by default.

The following property has a default value:

• mail.smtp.ssl.protocols has a default value of TLSv1 TLSv1.1 TLSv1.2.

Since version 1.44.0, the following two properties have default values:

• mail.smtp.timeout has a default value of 2000.
• mail.smtp.connectiontimeout has a default value of 2000.

Here's an example value which overrides these properties; in this case setting both timeout defaults to 5 seconds.

mail.smtp.timeout=5000\nmail.smtp.connectiontimeout=5000

The type of security protocol FusionAuth will use when connecting to the SMTP server. The possible values are:

• NONE - no security will be used. All communications will be sent plaintext.
• SSL - SSL will be used to connect to the SMTP server. This protocol is not recommended unless it is the only one your SMTP server supports.
• TLS - TLS will be used to connect to the SMTP server. This is the preferred protocol for all SMTP servers.

The Id of the Email Template that is used when a user had their account created for them and they must set their password manually and they are sent an email to set their password.

The Id of the Email Template used to send emails to users when a MFA method has been added to their account.

The Id of the Email Template used to notify a user when an administrator removes one of their MFA methods.

The Id of the Email Template used to send emails to users when a MFA method has been removed from their account.

When this value is set to true, the user is allowed to change their email address when they are gated because they haven't verified their email address.

The desired behavior during login for a user that does not have a verified email. The possible values are:

• Allow - the user will be allowed to complete login.
• Gated - verification is required before a user can complete login. The use of this value will require a paid plan.

An optional username FusionAuth will to authenticate with the SMTP server.

The Id of the Email Template used to send emails to users to verify that their email address is valid. If either the verifyEmail or verifyEmailWhenChanged fields are true, this field is required.

The process by which the user will verify their email address. The possible values are:

• ClickableLink - send the user a code with a clickable link.
• FormField - send the user a short code intended to be manually entered into a form field. This is only available when tenant.emailConfiguration.unverified.behavior has the Gated value.

Whether the user's email addresses are verified when the registers with your application.

Whether the user's email addresses are verified when the user changes them.

A mapping of the configuration for each event type that FusionAuth sends. The event types that are the keys into this Object are:

• audit-log.create - When an audit log is created Available since 1.30.0
• event-log.create - When an event log is created Available since 1.30.0
• jwt.public-key.update - When a JWT signing Public / Private keypair may have been changed
• jwt.refresh - When an access token is refreshed using a refresh token Available since 1.16.0
• jwt.refresh-token.revoke - When a JWT Refresh Token is revoked
• kickstart.success - When kickstart has successfully completed Available since 1.30.0
• user.action - When a user action is triggered
• user.bulk.create - When multiple users are created in bulk (i.e. during an import)
• user.create - When a user is created
• user.create.complete - When a user create transaction has completed Available since 1.30.0
• user.deactivate - When a user is deactivated
• user.delete - When a user is deleted
• user.delete.complete - When a user delete transaction has completed Available since 1.30.0
• user.email.update - When a user updates their email address Available since 1.30.0
• user.email.verified - When a user verifies their email address Available since 1.8.0
• user.identity-provider.link - When a link is created from a user to an Identity Provider Available since 1.36.0
• user.identity-provider.unlink - When an existing Identity Provider link is removed from a User Available since 1.36.0
• user.identity.verified - When a user's identity is verified Available since 1.59.0
• user.loginId.duplicate.create - When a request to create a user with a login Id (email or username) which is already in use has been received Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.loginId.duplicate.update - When a request to update a user and change their login Id (email or username) to one that is already in use has been received Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.login.failed - When a user fails a login request Available since 1.6.0
• user.login.new-device - When a user begins a login request with a new device Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.login.success - When a user completes a login request Available since 1.6.0
• user.login.suspicious - When a user logs in and is considered to be a potential threat (requires an activated Enterprise license) Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.password.breach - When Reactor detects a user is using a potentially breached password (requires an activated license) Available since 1.15.0

  Note: To use , you'll need a paid plan.

• user.password.reset.send - When a forgot password email has been sent to a user Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.password.reset.start - When the process to reset a user password has started Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.password.reset.success - When a user has successfully reset their password Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.password.update - When a user has updated their password Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.reactivate - When a user is reactivated
• user.registration.create - When a user registration is created Available since 1.6.0
• user.registration.create.complete - When a user registration create transaction has completed Available since 1.30.0
• user.registration.delete - When a user registration is deleted Available since 1.6.0
• user.registration.delete.complete - When a user registration delete transaction has completed Available since 1.30.0
• user.registration.update - When a user registration is updated Available since 1.6.0
• user.registration.update.complete - When a user registration update transaction has completed Available since 1.30.0
• user.registration.verified - When a user completes registration verification Available since 1.8.0
• user.two-factor.challenge - When a user is presented a two-factor challenge Available since 1.68.0

  Note: To use , you'll need an Enterprise plan.

• user.two-factor.failed-attempt - When a user submits an incorrect answer to a two-factor challenge Available since 1.68.0

  Note: To use , you'll need an Enterprise plan.

• user.two-factor.method.add - When a user has added a two-factor method Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.two-factor.method.remove - When a user has removed a two-factor method Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.two-factor.success - When a user submits a correct answer to a two-factor challenge Available since 1.68.0

  Note: To use , you'll need an Enterprise plan.

• user.update - When a user is updated
• user.update.complete - When a user update transaction has completed Available since 1.30.0

Whether or not FusionAuth should send these types of events to any configured Webhooks.

The transaction type that FusionAuth uses when sending these types of events to any configured Webhooks. The transaction types are:

• None - No Webhooks are required to succeed for the FusionAuth transaction to be committed.
• Any - Only a single Webhook is required to succeed for the FusionAuth transaction to be committed.
• SimpleMajority - A simple majority (50% or more) of Webhooks are required to succeed for the FusionAuth transaction to be committed.
• SuperMajority - A super majority (2/3 or more) of Webhooks are required to succeed for the FusionAuth transaction to be committed.
• AbsoluteMajority - Every Webhook must succeed for the FusionAuth transaction to be committed.

Prior to version 1.36.0, this value did not have a default. This meant at runtime the when the transaction type was calculated, it would be assumed to be AbsoluteMajority even though this value was not set in the domain.

The time in seconds until a OAuth authorization code in no longer valid to be exchanged for an access token. This is essentially the time allowed between the start of an Authorization request during the Authorization code grant and when you request an access token using this authorization code on the Token endpoint.

Value must be greater than 0 and less than or equal to 600.

Prior to version 1.28.0 this value was required.

The length of the secure generator used for generating the change password Id.

If the changePasswordIdGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the changePasswordIdGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the changePasswordIdGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the changePasswordIdGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

Prior to version 1.28.0 this value was required.

The type of the secure generator used for generating the change password Id. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

Prior to version 1.28.0 this value was required.

The time in seconds until a change password Id is no longer valid and cannot be used by the Change Password API. Value must be greater than 0.

Prior to version 1.28.0 this value was required.

The time in seconds until a device code Id is no longer valid and cannot be used by the Token API. Value must be greater than 0.

Prior to version 1.28.0 this value was required.

The length of the secure generator used for generating the device code Id.

If the deviceCodeTimeToLiveInSeconds.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the deviceCodeTimeToLiveInSeconds.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the deviceCodeTimeToLiveInSeconds.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the deviceCodeTimeToLiveInSeconds.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

Prior to version 1.28.0 this value was required.

The type of the secure generator used for generating the device code Id. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

Prior to version 1.28.0 this value was required.

The length of the secure generator used for generating the the email verification Id.

If the emailVerificationIdGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the emailVerificationIdGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the emailVerificationIdGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the emailVerificationIdGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

Prior to version 1.28.0 this value was required.

The type of the secure generator used for generating the email verification Id. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

Prior to version 1.28.0 this value was required.

The time in seconds until a email verification Id is no longer valid and cannot be used by the Verify Email API. Value must be greater than 0.

Prior to version 1.28.0 this value was required.

The length of the secure generator used for generating the email verification one time code.

If the emailVerificationOneTimeCodeGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the emailVerificationOneTimeCodeGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the emailVerificationOneTimeCodeGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the emailVerificationOneTimeCodeGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

The type of the secure generator used for generating the email verification one time code. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

The time in seconds until an external authentication Id is no longer valid and cannot be used by the Token API. Value must be greater than 0.

Prior to version 1.28.0 this value was required.

The time in seconds until an identity provider connection test Id is no longer valid and cannot be used by the Identity Provider Test API. Value must be greater than 0.

The time in seconds until a Login Timeout identifier is no longer valid to complete post-authentication steps in the OAuth workflow. Must be greater than 0.

The time in seconds until a One Time Password is no longer valid and cannot be used by the Login API. Value must be greater than 0.

Prior to version 1.28.0 this value was required.

The length of the secure generator used for generating the passwordless login.

If the passwordlessLoginGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the passwordlessLoginGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the passwordlessLoginGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the passwordlessLoginGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

Prior to version 1.28.0 this value was required.

The type of the secure generator used for generating the passwordless login. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

Prior to version 1.28.0 this value was required.

The length of the secure generator used for generating the passwordless one-time code login.

If the passwordlessLoginOneTimeCodeGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the passwordlessLoginOneTimeCodeGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the passwordlessLoginOneTimeCodeGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the passwordlessLoginOneTimeCodeGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

The type of the secure generator used for generating the passwordless one-time code login. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

The time in seconds until a passwordless code is no longer valid and cannot be used by the Passwordless API. Value must be greater than 0.

Prior to version 1.28.0 this value was required.

The number of seconds before the pending account link identifier is no longer valid to complete an account link request. Value must be greater than 0.

The length of the secure generator used for generating the the phone verification Id.

If the phoneVerificationIdGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the phoneVerificationIdGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the phoneVerificationIdGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the phoneVerificationIdGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

The type of the secure generator used for generating the phone verification Id. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

The time in seconds until a phone verification Id is no longer valid and cannot be used by the Verify Phone API. Value must be greater than 0.

The length of the secure generator used for generating the phone verification one time code.

If the phoneVerificationOneTimeCodeGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the phoneVerificationOneTimeCodeGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the phoneVerificationOneTimeCodeGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the phoneVerificationOneTimeCodeGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

The type of the secure generator used for generating the phone verification one time code. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

The length of the secure generator used for generating the registration verification Id.

If the registrationVerificationIdGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the registrationVerificationIdGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the registrationVerificationIdGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the registrationVerificationIdGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

Prior to version 1.28.0 this value was required.

The type of the secure generator used for generating the registration verification Id. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

Prior to version 1.28.0 this value was required.

The time in seconds until a registration verification Id is no longer valid and cannot be used by the Verify Registration API. Value must be greater than 0.

Prior to version 1.28.0 this value was required.

The length of the secure generator used for generating the registration verification one time code.

If the registrationVerificationIdGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the registrationVerificationIdGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the registrationVerificationIdGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the registrationVerificationIdGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

Prior to version 1.28.0 this value was required.

The type of the secure generator used for generating the registration verification one time code. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

Prior to version 1.28.0 this value was required.

The time in seconds until remembered OAuth scope consent choices are no longer valid, and the User will be prompted to consent to requested OAuth scopes even if they have not changed. Applies only when application.oauthConfiguration.consentMode is set to RememberDecision. Value must be greater than 0.

Note: To use advanced OAuth scopes, you'll need an Essentials or Enterprise plan.

The time in seconds that a SAML AuthN request Id returned by the Start SAML v2 Login Request API will be eligible to be used to complete a SAML v2 Login request.

The length of the secure generator used for generating the setup password Id.

If the setupPasswordIdGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the setupPasswordIdGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the setupPasswordIdGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the setupPasswordIdGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

Prior to version 1.28.0 this value was required.

The type of the secure generator used for generating the setup password Id. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

Prior to version 1.28.0 this value was required.

The time in seconds until a setup password Id is no longer valid and cannot be used by the Change Password API. Value must be greater than 0.

Prior to version 1.28.0 this value was required.

The number of seconds before the Trust Token is no longer valid to complete a request that requires trust. Value must be greater than 0.

The time in seconds until a two-factor Id is no longer valid and cannot be used by the Two-Factor Login API. Value must be greater than 0.

Prior to version 1.28.0 this value was required.

The length of the secure generator used for generating the the two-factor code Id.

If the twoFactorOneTimeCodeIdGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the twoFactorOneTimeCodeIdGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the twoFactorOneTimeCodeIdGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the twoFactorOneTimeCodeIdGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

Prior to version 1.28.0 this value was required.

The type of the secure generator used for generating the two-factor one time code Id. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

Prior to version 1.28.0 this value was required.

The number of seconds before the Two-Factor One Time Code used to enable or disable a two-factor method is no longer valid. Must be greater than 0.

Prior to version 1.28.0 this value was required.

The time in seconds until an issued Two-Factor trust Id is no longer valid and the User will be required to complete Two-Factor authentication during the next authentication attempt. Value must be greater than 0.

Prior to version 1.28.0 this value was required.

The time in seconds until a WebAuthn authentication challenge is no longer valid and the User will be required to restart the WebAuthn authentication ceremony by creating a new challenge. This value also controls the timeout for the client-side WebAuthn navigator.credentials.get API call. Value must be greater than 0.

Note: To use WebAuthn, you'll need a license.

The time in seconds until a WebAuthn registration challenge is no longer valid and the User will be required to restart the WebAuthn registration ceremony by creating a new challenge. This value also controls the timeout for the client-side WebAuthn navigator.credentials.create API call. Value must be greater than 0.

Note: To use WebAuthn, you'll need a license.

Indicates whether you want the user to be able to self-service unlock their account prior to the action duration by completing a password reset workflow.

The duration of the User Action. This value along with the actionDurationUnit will be used to set the duration of the User Action. Value must be greater than 0.

The unit of time associated with a duration. The possible values are:

• MINUTES
• HOURS
• DAYS
• WEEKS
• MONTHS
• YEARS

Indicates you would like to email the user when the user's account is locked due to this action being taken. This requires the User Action specified by the tenant.failedAuthenticationConfiguration.userActionId to also be configured for email. If the User Action is not configured to be able to email the user, this configuration will be ignored. See userEmailingEnabled on the User Action.

The email template configuration will be in the User Action.

The length of time in seconds before the failed authentication count will be reset. Value must be greater than 0.

For example, if tooManyAttempts is set to 5 and you fail to authenticate 4 times in a row, waiting for the duration specified here will cause your fifth attempt to start back at 1.

The number of failed attempts considered to be too many. Once this threshold is reached the specified User Action will be applied to the user for the duration specified. Value must be greater than 0.

The Id of the User Action that is applied when the threshold is reached for too many failed authentication attempts.

Whether to allow child registrations.

The unique Id of the email template to use when confirming a child.

Indicates that child users without parental verification will be permanently deleted after tenant.familyConfiguration.deleteOrphanedAccountsDays days.

The number of days from creation child users will be retained before being deleted for not completing parental verification. Value must be greater than 0.

Whether family configuration is enabled.

The unique Id of the email template to use when a family request is made.

The maximum age of a child. Value must be greater than 0.

The minimum age to be an owner. Value must be greater than 0.

Whether a parent email is required.

The unique Id of the email template to use for parent registration.

The unique Id of the form to use for the Add and Edit User form when used in the FusionAuth admin UI.

When this parameter is not provided, it will default to the form Id currently assigned to the Default tenant.

Note: To use custom forms, you'll need a paid plan.

Time in seconds until an inactive session will be invalidated. Used when creating a new session in the FusionAuth OAuth frontend.

The named issuer used to sign tokens. This is generally your public fully qualified domain with the https:// protocol prefix. For example, https://example.com.

Prior to version 1.30.0 this value was required.

The unique id of the signing key used to sign the access token.

Prior to version 1.30.0 this value was required.

The unique id of the signing key used to sign the Id token.

Prior to version 1.30.0 this value was required.

The Refresh Token expiration policy.

The possible values are:

• Fixed - the expiration is calculated from the time the token is issued.
• SlidingWindow - the expiration is calculated from the last time the token was used.
• SlidingWindowWithMaximumLifetime - the expiration is calculated from the last time the token was used, or until the maximumTimeToLiveInMinutes is reached.   Available since 1.46.0

The length of time specified in seconds that a one-time use token can be reused.

This value must be greater than 0 and less than 86400 which is equal to 24 hours. Setting this value to 0 effectively disables the grace period which means a one-time token may not be reused. For security reasons, you should keep this value as small as possible, and only increase past 0 to improve reliability for an asynchronous or clustered integration that may require a brief grace period.

Note that one-time use tokens refreshed within a grace period are not considered for revocation when tenant.jwtConfiguration.refreshTokenRevocationPolicy.onOneTimeTokenReuse is true. When a token is reused within the grace period the current token will be returned on the API response and the token will not be rotated.

When enabled, all of a user's refresh tokens will be revoked when a user action, such as locking an account based on a number of failed login attempts, prevents user login.

When enabled, all of a user's refresh tokens will be revoked when a user enables multi-factor authentication for the first time. This policy will not be applied when adding subsequent multi-factor methods to the user.

When enabled, if a one-time use refresh token is reused, the token will be revoked. This does not cause all refresh tokens to be revoked, only the reused token is revoked.

When enabled, all of a user's refresh tokens will be revoked when a user changes their password.

The maximum lifetime of a refresh token when using a refreshTokenExpirationPolicy of SlidingWindowWithMaximumLifetime. Value must be greater than 0.

When refreshTokenExpirationPolicy is set to SlidingWindowWithMaximumLifetime, this value must be greater than or equal to refreshTokenTimeToLiveInMinutes.

The length of time in minutes a Refresh Token is valid from the time it was issued. Value must be greater than 0.

Prior to version 1.28.0 this value was required.

The refresh token usage policy. The following are valid values:

• Reusable - the token does not change after it was issued.
• OneTimeUse - the token value will be changed each time the token is used to refresh a JWT. The client must store the new value after each usage.

Prior to version 1.28.0 this value was required.

The length of time in seconds this JWT is valid from the time it was issued. Value must be greater than 0.

Prior to version 1.28.0 this value was required.

The Id of the lambda that will be invoked at the end of a successful login request in order to extend custom validation of a login request.

The Id of the lambda that will be invoked during logins, password changes, and MFA Status API calls to perform various validations to decide whether to challenge the user on one of their MFA methods.

Note: To use Multi-Factor Requirement Lambdas, you'll need an Enterprise plan.

The Id of a SCIM User Request lambda that will be used to convert the SCIM Enterprise User request to a FusionAuth User.

Note: To use SCIM, you'll need an Enterprise plan.

Required when tenant.scimServerConfiguration.enabled is true.

The Id of a SCIM User Response lambda that will be used to convert a FusionAuth Enterprise User to a SCIM Server response.

Note: To use SCIM, you'll need an Enterprise plan.

Required when tenant.scimServerConfiguration.enabled is true.

The Id of a SCIM Group Request lambda that will be used to convert the SCIM Group request to a FusionAuth Group.

Note: To use SCIM, you'll need an Enterprise plan.

Required when tenant.scimServerConfiguration.enabled is true.

The Id of a SCIM Group Response lambda that will be used to convert a FusionAuth Group to a SCIM Server response.

Note: To use SCIM, you'll need an Enterprise plan.

Required when tenant.scimServerConfiguration.enabled is true.

The Id of a SCIM User Request lambda that will be used to convert the SCIM User request to a FusionAuth User.

Note: To use SCIM, you'll need an Enterprise plan.

Required when tenant.scimServerConfiguration.enabled is true.

The Id of a SCIM User Response lambda that will be used to convert a FusionAuth User to a SCIM Server response.

Note: To use SCIM, you'll need an Enterprise plan.

Required when tenant.scimServerConfiguration.enabled is true.

The logout redirect URL when sending the user's browser to the /oauth2/logout URI of the FusionAuth Front End. This value is only used when a logout URL is not defined in your Application.

Indicates whether to require an API key for the Login API when an applicationId is not provided. When an applicationId is provided to the Login API call, the application configuration will take precedence.

In almost all cases, you will want to this to be true.

The logout redirect URL when sending the user's browser to the /oauth2/logout URI of the FusionAuth Front End. This value is only used when a logout URL is not defined in your Application.

The password maximum age in days. The number of days after which FusionAuth will require a user to change their password. Required when tenant.maximumPasswordAge.enabled is set to true.

Indicates that the maximum password age is enabled and being enforced.

The password minimum age in seconds. When enabled FusionAuth will not allow a password to be changed until it reaches this minimum age. Required when tenant.minimumPasswordAge.enabled is set to true.

Indicates that the minimum password age is enabled and being enforced.

When enabled, users may utilize an authenticator application to complete a multi-factor authentication request. This method uses TOTP (Time-Based One-Time Password) as defined in RFC 6238 and often uses an native mobile app such as Google Authenticator.

Determines if debug should be enabled for this tenant to create an event log message to assist in tracing Intelligent MFA.

When enabled, users may utilize an email address to complete a multi-factor authentication request.

The Id of the email template that is used when notifying a user to complete a multi-factor authentication request. This field is required when tenant.multiFactorConfiguration.email.enabled is set to true.

When set to Enabled and a user has one or more two-factor methods configured, the user will be required to complete a two-factor challenge during login. When set to Disabled, even when a user has configured one or more two-factor methods, the user will not be required to complete a two-factor challenge during login. When set to Required, a two-factor challenge will be required during login. If a user has not configured any two-factor methods, they will not be able to log in.

Risk-based policies use FusionAuth's Intelligent MFA, which combines multiple signals to decide when to issue an MFA challenge.

This value may be overridden by the value configured by the application.multiFactorConfiguration.loginPolicy.

Supported values include:

• Enabled - Require a two-factor challenge during login when an eligible method is available.
• Disabled - Do not require a two-factor challenge during login.
• ChallengeOnMediumRisk - Only challenge on medium or high login risk Available since 1.68.0
• ChallengeOnHighRisk - Only challenge on high login risk Available since 1.68.0
• Required - Require a two-factor challenge during login. A user will be required to configure 2FA if no eligible methods are available. Available since 1.42.0

Note: To use an Intelligent MFA Policy, you'll need a paid plan.

When enabled, users may utilize a mobile phone number to complete a multi-factor authentication request.

The messenger that is used to deliver a SMS multi-factor authentication request. This field is required when tenant.multiFactorConfiguration.sms.enabled is set to true.

The Id of the SMS template that is used when notifying a user to complete a multi-factor authentication request. This field is required when tenant.multiFactorConfiguration.sms.enabled is set to true.

When enabled, users can receive a spoken multi-factor authentication code over a phone call.

The messenger that is used to deliver a voice multi-factor authentication request. This field is required when tenant.multiFactorConfiguration.voice.enabled is set to true.

The Id of the voice template that is used when notifying a user to complete a multi-factor authentication request. This field is required when tenant.multiFactorConfiguration.voice.enabled is set to true.

The unique name of the Tenant.

The Id of a lambda that will be called to populate the JWT during a client credentials grant.

Note: To use client credentials grant, you'll need a paid plan.

The default method for encrypting the User's password. The following encryptors are provided with FusionAuth:

• salted-md5
• salted-sha256
• salted-hmac-sha256
• salted-pbkdf2-hmac-sha256
• salted-pbkdf2-hmac-sha256-512
• salted-pbkdf2-hmac-sha512-512
• bcrypt
• phpass-md5
• phpass-sha512

The factor used by the password encryption scheme. If not provided, the PasswordEncryptor provides a default value. Generally this will be used as an iteration count to generate the hash. The actual use of this value is up to the PasswordEncryptor implementation.

When enabled a user's hash configuration will be modified to match these configured settings. This can be useful to increase a password hash strength over time or upgrade imported users to a more secure encryption scheme after an initial import.

Beginning in version 1.42.0 when this configuration is enabled, in addition to re-hashing on login, the password will be re-hashed on password change as well.

Whether to enable Reactor breach detection. Requires an activated license.

The level of severity where Reactor will consider a breach. The following are valid values:

• High Only requires a password match, this is the most secure and is recommended
• Medium Exact match on username, email address or email sub-address
• Low Exact match on an email or username, or the password is a common breached value

The Id of the email template to use when notifying user of breached password. Required if tenant.passwordValidationRules.breachDetection.onLogin is set to NotifyUser.

The behavior when detecting breaches at time of user login. The following are valid values:

• Off Do not perform breach detection at login
• RecordOnly Only record the result, take no action
• NotifyUser Notify the end user via email
• RequireChange Require immediate password change

Whether to reject passwords which contain the user's login Id.

The maximum length of a password when a new user is created or a user requests a password change.

This value must be greater than 0 and less than or equal to 256. When passwordEncryptionConfiguration.encryptionScheme is equal to bcrypt, the maximum will be limited to 50.

The minimum length of a password when a new user is created or a user requests a password change.

The number of previous passwords to remember. Value must be greater than 0.

Whether to prevent a user from using any of their previous passwords.

Whether to force the user to use at least one uppercase and one lowercase character.

Whether to force the user to use at least one non-alphanumeric character.

Whether to force the user to use at least one number.

When enabled the user's password will be validated during login. If the password does not meet the currently configured validation rules the user will be required to change their password.

The additional SMTP headers to be added to each outgoing email. Each SMTP header consists of a name and a value.

Determines if debug should be enabled to create an event log to assist in debugging SMTP errors.

The default email address that emails will be sent from when a from address is not provided on an individual email template. This is the address part email address (i.e. Jared Dunn jared@piedpiper.com).

The default From Name used in sending emails when a from name is not provided on an individual email template. This is the display name part of the email address ( i.e. Jared Dunn jared@piedpiper.com).

The Id of the Email Template used to send emails to users when their email address is updated.

Note: To use advanced threat detection emails, you'll need an Enterprise plan.

The Id of the Email Template used to notify a user that their email address has been verified.

The Id of the Email Template that is used when a user is sent a forgot password email.

The host name of the SMTP server that FusionAuth will use.

Prior to version 1.28.0 this value was required.

When set to true, this allows email to be verified as a result of completing a similar email based workflow such as change password. When set to false, the user must explicitly complete the email verification workflow even if the user has already completed a similar email workflow such as change password.

The Id of the Email Template used to send emails to users when another user attempts to create an account with their login Id.

Note: To use advanced threat detection emails, you'll need an Enterprise plan.

The Id of the Email Template used to send emails to users when another user attempts to update an existing account to use their login Id.

The Id of the Email Template used to send emails to users when they log in on a new device.

Note: To use advanced threat detection emails, you'll need an Enterprise plan.

The Id of the Email Template used to send emails to users when a suspicious login occurs.

Note: To use advanced threat detection emails, you'll need an Enterprise plan.

An optional password FusionAuth will use to authenticate with the SMTP server.

The Id of the Passwordless Email Template, sent to users when they start a passwordless login.

The Id of the Email Template used to send emails to users when they have completed a 'forgot password' workflow and their password has been reset.

Note: To use advanced threat detection emails, you'll need an Enterprise plan.

The Id of the Email Template used to send emails to users when their password has been updated.

Note: To use advanced threat detection emails, you'll need an Enterprise plan.

The port of the SMTP server that FusionAuth will use.

Prior to version 1.28.0 this value was required.

Custom SMTP configuration properties that may be necessary in some cases. This can contain any Java mail property. It will override anything FusionAuth sets by default.

The following property has a default value:

• mail.smtp.ssl.protocols has a default value of TLSv1 TLSv1.1 TLSv1.2.

Since version 1.44.0, the following two properties have default values:

• mail.smtp.timeout has a default value of 2000.
• mail.smtp.connectiontimeout has a default value of 2000.

Here's an example value which overrides these properties; in this case setting both timeout defaults to 5 seconds.

mail.smtp.timeout=5000\nmail.smtp.connectiontimeout=5000

The type of security protocol FusionAuth will use when connecting to the SMTP server. The possible values are:

• NONE - no security will be used. All communications will be sent plaintext.
• SSL - SSL will be used to connect to the SMTP server. This protocol is not recommended unless it is the only one your SMTP server supports.
• TLS - TLS will be used to connect to the SMTP server. This is the preferred protocol for all SMTP servers.

The Id of the Email Template that is used when a user had their account created for them and they must set their password manually and they are sent an email to set their password.

The Id of the Email Template used to send emails to users when a MFA method has been added to their account.

Note: To use advanced threat detection emails, you'll need an Enterprise plan.

The Id of the Email Template used to notify a user when an administrator removes one of their MFA methods.

The Id of the Email Template used to send emails to users when a MFA method has been removed from their account.

Note: To use advanced threat detection emails, you'll need an Enterprise plan.

When this value is set to true, the user is allowed to change their email address when they are gated because they haven't verified their email address.

The desired behavior during login for a user that does not have a verified email. The possible values are:

• Allow - the user will be allowed to complete login.
• Gated - verification is required before a user can complete login. The use of this value will require a paid plan.

An optional username FusionAuth will to authenticate with the SMTP server.

The Id of the Email Template used to send emails to users to verify that their email address is valid. If either the verifyEmail or verifyEmailWhenChanged fields are true, this field is required.

The process by which the user will verify their email address. The possible values are:

• ClickableLink - send the user a code with a clickable link.
• FormField - send the user a short code intended to be manually entered into a form field. This is only available when tenant.emailConfiguration.unverified.behavior has the Gated value.

Whether the user's email addresses are verified when the registers with your application.

Whether the user's email addresses are verified when the user changes them.

Whether rate limiting is enabled for failed login.

Note: To use rate limiting, you'll need an Enterprise plan.

The number of times a user can fail to login within the configured timePeriodInSeconds duration. If a Failed authentication action has been configured then it will take precedence.

Required when enabled is set to true.

Note: To use rate limiting, you'll need an Enterprise plan.

The duration for the number of times a user can fail login before being rate limited.

Required when enabled is set to true.

Note: To use rate limiting, you'll need an Enterprise plan.

Whether rate limiting is enabled for forgot password.

Note: To use rate limiting, you'll need an Enterprise plan.

The number of times a user can request a forgot password email within the configured timePeriodInSeconds duration.

Required when enabled is set to true.

Note: To use rate limiting, you'll need an Enterprise plan.

The duration for the number of times a user can request a forgot password email before being rate limited.

Required when enabled is set to true.

Note: To use rate limiting, you'll need an Enterprise plan.

Whether rate limiting is enabled for send email verification.

Note: To use rate limiting, you'll need an Enterprise plan.

The number of times a user can request a verification email within the configured timePeriodInSeconds duration.

Required when enabled is set to true.

Note: To use rate limiting, you'll need an Enterprise plan.

The duration for the number of times a user can request a verification email before being rate limited.

Required when enabled is set to true.

Note: To use rate limiting, you'll need an Enterprise plan.

Whether rate limiting is enabled for sending passwordless login links/codes via email.

Note: To use rate limiting, you'll need an Enterprise plan.

The number of times a user can request a passwordless login email within the configured timePeriodInSeconds duration.

Required when enabled is set to true.

Note: To use rate limiting, you'll need an Enterprise plan.

The duration for the number of times a user can request a passwordless login email before being rate limited.

Required when enabled is set to true.

Note: To use rate limiting, you'll need an Enterprise plan.

Whether rate limiting is enabled for sending passwordless login links/codes via SMS.

Note: To use rate limiting, you'll need an Enterprise plan.

The number of times a user can request a passwordless login SMS message within the configured timePeriodInSeconds duration.

Required when enabled is set to true.

Note: To use rate limiting, you'll need an Enterprise plan.

The duration for the number of times a user can request a passwordless login SMS message before being rate limited.

Required when enabled is set to true.

Note: To use rate limiting, you'll need an Enterprise plan.

Whether rate limiting is enabled for send phone verification.

Note: To use rate limiting, you'll need an Enterprise plan.

The number of times a user can request a phone verification message within the configured timePeriodInSeconds duration.

Required when enabled is set to true.

Note: To use rate limiting, you'll need an Enterprise plan.

The duration for the number of times a user can request a phone verification message before being rate limited.

Required when enabled is set to true.

Note: To use rate limiting, you'll need an Enterprise plan.

Whether rate limiting is enabled for send registration verification.

Note: To use rate limiting, you'll need an Enterprise plan.

The number of times a user can request a registration verification email within the configured timePeriodInSeconds duration.

Required when enabled is set to true.

Note: To use rate limiting, you'll need an Enterprise plan.

The duration for the number of times a user can request a registration verification email before being rate limited.

Required when enabled is set to true.

Note: To use rate limiting, you'll need an Enterprise plan.

Whether rate limiting is enabled for send two-factor.

Note: To use rate limiting, you'll need an Enterprise plan.

The number of times a user can request a two-factor code by email or SMS within the configured timePeriodInSeconds duration.

Required when enabled is set to true.

Note: To use rate limiting, you'll need an Enterprise plan.

The duration for the number of times a user can request a two-factor code by email or SMS before being rate limited.

Required when enabled is set to true.

Note: To use rate limiting, you'll need an Enterprise plan.

A list of unique domains that are not allowed to register when self service is enabled.

Note: To use blocked domains, you'll need an Enterprise plan.

The Entity Type that will be used to represent SCIM Clients for this tenant.

Note: To use SCIM, you'll need an Enterprise plan.

Required when tenant.scimServerConfiguration.enabled is true.

Whether or not this tenant has the SCIM endpoints enabled.

Note: To use SCIM, you'll need an Enterprise plan.

JSON formatted as a SCIM Schemas endpoint response. Because the SCIM lambdas may modify the JSON response, ensure the Schema's response matches that generated by the response lambdas. More about Schema definitions.

When this parameter is not provided, it will default to EnterpriseUser, Group, and User schema definitions as defined by the SCIM core schemas spec.

Note: To use SCIM, you'll need an Enterprise plan.

The Entity Type that will be used to represent SCIM Servers for this tenant.

Note: To use SCIM, you'll need an Enterprise plan.

Required when tenant.scimServerConfiguration.enabled is true.

The number of seconds before a trusted device is reset. When reset, a user is forced to complete captcha during login and complete two-factor authentication if applicable.

When enabled, an SSO session can be created after login by providing an access token as a bearer token in a request to the OAuth2 Authorize endpoint.

The unique Id of the theme to be used to style the login page and other end user templates.

Prior to version 1.30.0 this value was required.

Indicates that users with neither a verified email address nor a verified phone number will be permanently deleted after tenant.userDeletePolicy.unverified.numberOfDaysToRetain days.

The number of days from creation users will be retained before being deleted for not completing email or phone number verification. This field is required when tenant.userDeletePolicy.unverified.enabled is set to true. Value must be greater than 0.

When true, FusionAuth will handle username collisions by generating a random suffix.

Note: To use unique usernames, you'll need a paid plan.

The maximum number of digits to use when building a unique suffix for a username. A number will be randomly selected and will be 1 or more digits up to this configured value in length. For example, if this value is 5, the suffix will be a number between 00001 and 99999, inclusive. The value of this field must be greater than or equal to 3 and less than or equal to 10.

A single character to use as a separator from the requested username and a unique suffix that is added when a duplicate username is detected. This value can be a single non-alphanumeric ASCII character.

This strategy instructions FusionAuth when to append a unique suffix to the username. The possible values are:

• Always - Always append a unique suffix even when the requested username is not in use.
• OnCollision - Only append a unique suffix when the requested username is in use.

Determines the authenticator attachment requirement for WebAuthn passkey registration when using the bootstrap workflow. The possible values are:

• any - An authenticator with any attachment modality will be allowed during registration.
• crossPlatform - Only authenticators with the cross-platform attachment modality will be allowed during registration. These are also referred to as "roaming" authenticators.
• platform - Only authenticators with the platform attachment modality will be allowed during registration.

The recommended value for the bootstrap workflow is any.

Note: To use WebAuthn, you'll need a license.

Note: To use WebAuthn cross-platform authenticators, you'll need an Enterprise plan.

Whether or not this tenant has the WebAuthn bootstrap workflow enabled. The bootstrap workflow is used when the user must "bootstrap" the authentication process by identifying themselves prior to the WebAuthn ceremony and can be used to authenticate from a new device using WebAuthn.

Note: To use WebAuthn, you'll need a license.

Determines the user verification requirement for WebAuthn passkey registration and authentication when using the bootstrap workflow. The possible values are:

• discouraged - If possible, do not require user verification during registration and authentication.
• preferred - Prefer authenticators that support user verification during registration and authentication but allow others.
• required - Only authenticators that support user verification will be allowed.

It is highly recommended to use the required option for the bootstrap workflow.

Note: To use WebAuthn, you'll need a license.

Determines if debug should be enabled for this tenant to create an event log to assist in debugging WebAuthn errors.

Note: To use WebAuthn, you'll need a license.

Whether or not this tenant has WebAuthn enabled globally.

Note: To use WebAuthn, you'll need a license.

Determines the authenticator attachment requirement for WebAuthn passkey registration when using the reauthentication workflow. The possible values are:

• any - An authenticator with any attachment modality will be allowed during registration.
• crossPlatform - Only authenticators with the cross-platform attachment modality will be allowed during registration. These are also referred to as "roaming" authenticators.
• platform - Only authenticators with the platform attachment modality will be allowed during registration.

The recommended value for the reauthentication workflow is platform.

Note: To use WebAuthn, you'll need a license.

Note: To use WebAuthn cross-platform authenticators, you'll need an Enterprise plan.

Whether or not this tenant has the WebAuthn reauthentication workflow enabled. The reauthentication workflow will automatically prompt a user to authenticate using WebAuthn for repeated logins from the same device.

Note: To use WebAuthn, you'll need a license.

Determines the user verification requirement for WebAuthn passkey registration and authentication when using the reauthentication workflow. The possible values are:

• discouraged - If possible, do not require user verification during registration and authentication.
• preferred - Prefer authenticators that support user verification during registration and authentication but allow others.
• required - Only authenticators that support user verification will be allowed.

It is highly recommended to use the required option for the reauthentication workflow.

Note: To use WebAuthn, you'll need a license.

The value this tenant will use for the Relying Party Id in WebAuthn ceremonies. Passkeys can only be used to authenticate on sites using the same Relying Party Id they were registered with. This value must match the browser origin or be a registrable domain suffix of the browser origin. For example, if your domain is auth.piedpiper.com, you could use auth.piedpiper.com or piedpiper.com but not m.auth.piedpiper.com or com.

When this parameter is omitted, FusionAuth will use null for the Relying Party Id in passkey creation and request options. A null value in the WebAuthn JavaScript API will use the browser origin.

Note: To use WebAuthn, you'll need a license.

The value this tenant will use for the Relying Party name in WebAuthn ceremonies. This value may be displayed by browser or operating system dialogs during WebAuthn ceremonies.

When this parameter is omitted, FusionAuth will use the tenant.issuer value.

Note: To use WebAuthn, you'll need a license.

An array of Webhook Ids. For Webhooks that are not already configured for All Tenants, specifying an Id on this request will indicate the associated Webhook should handle events for this tenant.

The Id to use for the new Tenant. If not specified a secure random UUID will be generated.

The Id of an existing Tenant from which a copy will be made. All other values will be copied from the source Tenant to the new Tenant.

The unique name of the Tenant.

The Id of the IP Access Control List limiting access to this all applications in this tenant.

The default base URL used when rendering links in templates for this Tenant. This value is used when application.baseURL is not defined.

The type of captcha method to use.

Whether captcha configuration is enabled.

The secret key for this captcha method.

The site key for this captcha method.

The numeric threshold which separates a passing score from a failing one. This value only applies if using either the Google v3 or HCaptcha Enterprise method, otherwise this value is ignored.

Indicates the tenant has been configured. It is always true, except for default tenant when the setup wizard has not been completed, in which case it is false.

A list of Connector policies. Users will be authenticated against Connectors in order. Each Connector can be included in this list at most once and must exist.

The identifier of the Connector to which this policy refers.

An list of email domains to which this connector should apply.

A value of ["*"] indicates this connector applies to all users.

If true, the user's data will be migrated to FusionAuth at first successful authentication; subsequent authentications will occur against the FusionAuth datastore. If false, the Connector's source will be treated as authoritative.

An object that can hold any information about the Tenant that should be persisted.

The additional SMTP headers to be added to each outgoing email. Each SMTP header consists of a name and a value.

Determines if debug should be enabled to create an event log to assist in debugging SMTP errors.

The default email address that emails will be sent from when a from address is not provided on an individual email template. This is the address part email address (i.e. Jared Dunn jared@piedpiper.com).

The default From Name used in sending emails when a from name is not provided on an individual email template. This is the display name part of the email address ( i.e. Jared Dunn jared@piedpiper.com).

The Id of the Email Template used to send emails to users when their email address is updated.

The Id of the Email Template used to notify a user that their email address has been verified.

The Id of the Email Template that is used when a user is sent a forgot password email.

The host name of the SMTP server that FusionAuth will use.

Prior to version 1.28.0 this value was required.

When set to true, this allows email to be verified as a result of completing a similar email based workflow such as change password. When set to false, the user must explicitly complete the email verification workflow even if the user has already completed a similar email workflow such as change password.

The Id of the Email Template used to send emails to users when another user attempts to create an account with their login Id.

The Id of the Email Template used to send emails to users when another user attempts to update an existing account to use their login Id.

The Id of the Email Template used to send emails to users when they log in on a new device.

The Id of the Email Template used to send emails to users when a suspicious login occurs.

An optional password FusionAuth will use to authenticate with the SMTP server.

The Id of the Passwordless Email Template, sent to users when they start a passwordless login.

The Id of the Email Template used to send emails to users when they have completed a 'forgot password' workflow and their password has been reset.

The Id of the Email Template used to send emails to users when their password has been updated.

The port of the SMTP server that FusionAuth will use.

Prior to version 1.28.0 this value was required.

Custom SMTP configuration properties that may be necessary in some cases. This can contain any Java mail property. It will override anything FusionAuth sets by default.

The following property has a default value:

• mail.smtp.ssl.protocols has a default value of TLSv1 TLSv1.1 TLSv1.2.

Since version 1.44.0, the following two properties have default values:

• mail.smtp.timeout has a default value of 2000.
• mail.smtp.connectiontimeout has a default value of 2000.

Here's an example value which overrides these properties; in this case setting both timeout defaults to 5 seconds.

mail.smtp.timeout=5000\nmail.smtp.connectiontimeout=5000

The type of security protocol FusionAuth will use when connecting to the SMTP server. The possible values are:

• NONE - no security will be used. All communications will be sent plaintext.
• SSL - SSL will be used to connect to the SMTP server. This protocol is not recommended unless it is the only one your SMTP server supports.
• TLS - TLS will be used to connect to the SMTP server. This is the preferred protocol for all SMTP servers.

The Id of the Email Template that is used when a user had their account created for them and they must set their password manually and they are sent an email to set their password.

The Id of the Email Template used to send emails to users when a MFA method has been added to their account.

The Id of the Email Template used to notify a user when an administrator removes one of their MFA methods.

The Id of the Email Template used to send emails to users when a MFA method has been removed from their account.

When this value is set to true, the user is allowed to change their email address when they are gated because they haven't verified their email address.

The desired behavior during login for a user that does not have a verified email. The possible values are:

• Allow - the user will be allowed to complete login.
• Gated - verification is required before a user can complete login. The use of this value will require a paid plan.

An optional username FusionAuth will to authenticate with the SMTP server.

The Id of the Email Template used to send emails to users to verify that their email address is valid. If either the verifyEmail or verifyEmailWhenChanged fields are true, this field is required.

The process by which the user will verify their email address. The possible values are:

• ClickableLink - send the user a code with a clickable link.
• FormField - send the user a short code intended to be manually entered into a form field. This is only available when tenant.emailConfiguration.unverified.behavior has the Gated value.

Whether the user's email addresses are verified when the registers with your application.

Whether the user's email addresses are verified when the user changes them.

A mapping of the configuration for each event type that FusionAuth sends. The event types that are the keys into this Object are:

• audit-log.create - When an audit log is created Available since 1.30.0
• event-log.create - When an event log is created Available since 1.30.0
• jwt.public-key.update - When a JWT signing Public / Private keypair may have been changed
• jwt.refresh - When an access token is refreshed using a refresh token Available since 1.16.0
• jwt.refresh-token.revoke - When a JWT Refresh Token is revoked
• kickstart.success - When kickstart has successfully completed Available since 1.30.0
• user.action - When a user action is triggered
• user.bulk.create - When multiple users are created in bulk (i.e. during an import)
• user.create - When a user is created
• user.create.complete - When a user create transaction has completed Available since 1.30.0
• user.deactivate - When a user is deactivated
• user.delete - When a user is deleted
• user.delete.complete - When a user delete transaction has completed Available since 1.30.0
• user.email.update - When a user updates their email address Available since 1.30.0
• user.email.verified - When a user verifies their email address Available since 1.8.0
• user.identity-provider.link - When a link is created from a user to an Identity Provider Available since 1.36.0
• user.identity-provider.unlink - When an existing Identity Provider link is removed from a User Available since 1.36.0
• user.identity.verified - When a user's identity is verified Available since 1.59.0
• user.loginId.duplicate.create - When a request to create a user with a login Id (email or username) which is already in use has been received Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.loginId.duplicate.update - When a request to update a user and change their login Id (email or username) to one that is already in use has been received Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.login.failed - When a user fails a login request Available since 1.6.0
• user.login.new-device - When a user begins a login request with a new device Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.login.success - When a user completes a login request Available since 1.6.0
• user.login.suspicious - When a user logs in and is considered to be a potential threat (requires an activated Enterprise license) Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.password.breach - When Reactor detects a user is using a potentially breached password (requires an activated license) Available since 1.15.0

  Note: To use , you'll need a paid plan.

• user.password.reset.send - When a forgot password email has been sent to a user Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.password.reset.start - When the process to reset a user password has started Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.password.reset.success - When a user has successfully reset their password Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.password.update - When a user has updated their password Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.reactivate - When a user is reactivated
• user.registration.create - When a user registration is created Available since 1.6.0
• user.registration.create.complete - When a user registration create transaction has completed Available since 1.30.0
• user.registration.delete - When a user registration is deleted Available since 1.6.0
• user.registration.delete.complete - When a user registration delete transaction has completed Available since 1.30.0
• user.registration.update - When a user registration is updated Available since 1.6.0
• user.registration.update.complete - When a user registration update transaction has completed Available since 1.30.0
• user.registration.verified - When a user completes registration verification Available since 1.8.0
• user.two-factor.challenge - When a user is presented a two-factor challenge Available since 1.68.0

  Note: To use , you'll need an Enterprise plan.

• user.two-factor.failed-attempt - When a user submits an incorrect answer to a two-factor challenge Available since 1.68.0

  Note: To use , you'll need an Enterprise plan.

• user.two-factor.method.add - When a user has added a two-factor method Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.two-factor.method.remove - When a user has removed a two-factor method Available since 1.30.0

  Note: To use , you'll need an Enterprise plan.

• user.two-factor.success - When a user submits a correct answer to a two-factor challenge Available since 1.68.0

  Note: To use , you'll need an Enterprise plan.

• user.update - When a user is updated
• user.update.complete - When a user update transaction has completed Available since 1.30.0

Whether or not FusionAuth should send these types of events to any configured Webhooks.

The transaction type that FusionAuth uses when sending these types of events to any configured Webhooks. The transaction types are:

• None - No Webhooks are required to succeed for the FusionAuth transaction to be committed.
• Any - Only a single Webhook is required to succeed for the FusionAuth transaction to be committed.
• SimpleMajority - A simple majority (50% or more) of Webhooks are required to succeed for the FusionAuth transaction to be committed.
• SuperMajority - A super majority (2/3 or more) of Webhooks are required to succeed for the FusionAuth transaction to be committed.
• AbsoluteMajority - Every Webhook must succeed for the FusionAuth transaction to be committed.

The time in seconds until an OAuth authorization code is no longer valid to be exchanged for an access token. This is essentially the time allowed between the start of an Authorization request during the Authorization code grant and when you request an access token using this authorization code on the Token endpoint.

Value must be greater than 0 and less than or equal to 600.

The length of the secure generator used for generating the change password Id.

If the changePasswordIdGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the changePasswordIdGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the changePasswordIdGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the changePasswordIdGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

The type of the secure generator used for generating the change password Id. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

The time in seconds until a change password Id is no longer valid and cannot be used by the Change Password API. Value must be greater than 0.

The time in seconds until a device code Id is no longer valid and cannot be used by the Token API. Value must be greater than 0.

The length of the secure generator used for generating the device code Id.

If the deviceCodeTimeToLiveInSeconds.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the deviceCodeTimeToLiveInSeconds.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the deviceCodeTimeToLiveInSeconds.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the deviceCodeTimeToLiveInSeconds.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

The type of the secure generator used for generating the device code Id. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

The length of the secure generator used for generating the the email verification Id.

If the emailVerificationIdGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the emailVerificationIdGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the emailVerificationIdGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the emailVerificationIdGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

The type of the secure generator used for generating the email verification Id. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

The time in seconds until an email verification Id is no longer valid and cannot be used by the Verify Email API. Value must be greater than 0.

The length of the secure generator used for generating the email verification one time code.

If the emailVerificationIdGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the emailVerificationIdGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the emailVerificationIdGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the emailVerificationIdGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

The type of the secure generator used for generating the email verification one time code. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

The time in seconds until an external authentication Id is no longer valid and cannot be used by the Token API. Value must be greater than 0.

The time in seconds until an identity provider connection test Id is no longer valid and cannot be used by the Identity Provider Test API. Value must be greater than 0.

The time in seconds until a Login Timeout identifier is no longer valid to complete post-authentication steps in the OAuth workflow. Must be greater than 0.

The time in seconds until a One Time Password is no longer valid and cannot be used by the Login API. Value must be greater than 0.

The length of the secure generator used for generating the passwordless login.

If the passwordlessLoginGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the passwordlessLoginGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the passwordlessLoginGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the passwordlessLoginGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

The type of the secure generator used for generating the passwordless login. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

The length of the secure generator used for generating the passwordless one-time login.

If the passwordlessLoginOneTimeCodeGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the passwordlessLoginOneTimeCodeGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the passwordlessLoginOneTimeCodeGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the passwordlessLoginOneTimeCodeGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

The type of the secure generator used for generating the passwordless one-time login. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

The time in seconds until a passwordless code is no longer valid and cannot be used by the Passwordless API. Value must be greater than 0.

The number of seconds before the pending account link identifier is no longer valid to complete an account link request.

The length of the secure generator used for generating the the phone verification Id.

If the phoneVerificationIdGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the phoneVerificationIdGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the phoneVerificationIdGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the phoneVerificationIdGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

The type of the secure generator used for generating the phone verification Id. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

The time in seconds until a phone verification Id is no longer valid and cannot be used by the Verify Phone API.

The length of the secure generator used for generating the phone verification one time code.

If the phoneVerificationOneTimeCodeGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the phoneVerificationOneTimeCodeGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the phoneVerificationOneTimeCodeGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the phoneVerificationOneTimeCodeGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

The type of the secure generator used for generating the phone verification one time code. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

The length of the secure generator used for generating the registration verification Id.

If the registrationVerificationIdGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the registrationVerificationIdGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the registrationVerificationIdGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the registrationVerificationIdGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

The type of the secure generator used for generating the registration verification Id. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

The time in seconds until a registration verification Id is no longer valid and cannot be used by the Verify Registration API. Value must be greater than 0.

The length of the secure generator used for generating the registration verification one time code.

If the registrationVerificationIdGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the registrationVerificationIdGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the registrationVerificationIdGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the registrationVerificationIdGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

The type of the secure generator used for generating the registration verification one time code. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

The time in seconds until remembered OAuth scope consent choices are no longer valid, and the User will be prompted to consent to requested OAuth scopes even if they have not changed. Applies only when application.oauthConfiguration.consentMode is set to RememberDecision. Value must be greater than 0.

The time in seconds that a SAML AuthN request Id returned by the Start SAML v2 Login Request API will be eligible to be used to complete a SAML v2 Login request.

The length of the secure generator used for generating the setup password Id.

If the setupPasswordIdGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the setupPasswordIdGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the setupPasswordIdGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the setupPasswordIdGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

The type of the secure generator used for generating the setup password Id. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

The time in seconds until a setup password Id is no longer valid and cannot be used by the Change Password API. Value must be greater than 0.

The number of seconds before the Trust Token is no longer valid to complete a request that requires trust. Value must be greater than 0.

The time in seconds until a two-factor Id is no longer valid and cannot be used by the Two-Factor Login API. Value must be greater than 0.

The length of the secure generator used for generating the the two-factor one time code Id.

If the twoFactorOneTimeCodeIdGenerator.type is equal to randomAlpha then the length must be greater or equal to 4 and less than or equal to 12. If the twoFactorOneTimeCodeIdGenerator.type is equal to randomAlphaNumeric then the length must be greater or equal to 4 and less than or equal to 12. If the twoFactorOneTimeCodeIdGenerator.type is equal to randomBytes then the length must be greater or equal to 16 and less than or equal to 128. If the twoFactorOneTimeCodeIdGenerator.type is equal to randomDigits then the length must be greater or equal to 4 and less than or equal to 12.

The type of the secure generator used for generating the two-factor code Id. Possible values are:

• randomAlpha
• randomAlphaNumeric
• randomBytes
• randomDigits

The number of seconds before the Two-Factor One Time Code used to enable or disable a two-factor method is no longer valid. Must be greater than 0.

The time in seconds until an issued Two-Factor trust Id is no longer valid and the User will be required to complete Two-Factor authentication during the next authentication attempt. Value must be greater than 0.

The time in seconds until a WebAuthn authentication challenge is no longer valid and the User will be required to restart the WebAuthn authentication ceremony by creating a new challenge. This value also controls the timeout for the client-side WebAuthn navigator.credentials.get API call. Value must be greater than 0.

The time in seconds until a WebAuthn registration challenge is no longer valid and the User will be required to restart the WebAuthn registration ceremony by creating a new challenge. This value also controls the timeout for the client-side WebAuthn navigator.credentials.create API call. Value must be greater than 0.

Indicates whether you want the user to be able to self-service unlock their account prior to the action duration by completing a password reset workflow.

The duration of the User Action. This value along with the actionDurationUnit will be used to set the duration of the User Action. Value must be greater than 0.

Indicates you would like to email the user when the user's account is locked due to this action being taken. This requires the User Action specified by the tenant.failedAuthenticationConfiguration.userActionId to also be configured for email. If the User Action is not configured to be able to email the user, this configuration will be ignored. See userEmailingEnabled on the User Action.

The length of time in seconds before the failed authentication count will be reset. Value must be greater than 0.

For example, if tooManyAttempts is set to 5 and you fail to authenticate 4 times in a row, waiting for the duration specified here will cause your fifth attempt to start back at 1.

The number of failed attempts considered to be too many. Once this threshold is reached the specified User Action will be applied to the user for the duration specified. Value must be greater than 0.

The Id of the User Action that is applied when the threshold is reached for too many failed authentication attempts.

Whether to allow child registrations.

The unique Id of the email template to use when confirming a child.

Indicates that child users without parental verification will be permanently deleted after tenant.familyConfiguration.deleteOrphanedAccountsDays days.

The number of days from creation child users will be retained before being deleted for not completing parental verification. Value must be greater than 0.

Whether family configuration is enabled.

The unique Id of the email template to use when a family request is made.

The maximum age of a child. Value must be greater than 0.

The minimum age to be an owner. Value must be greater than 0.

Whether a parent email is required.

The unique Id of the email template to use for parent registration.

The unique Id of the form to use for the Add and Edit User form when used in the FusionAuth admin UI.

Time in seconds until an inactive session will be invalidated. Used when creating a new session in the FusionAuth OAuth frontend.

The unique identifier for this Tenant.

The instant that the Tenant was added to the FusionAuth database.

The named issuer used to sign tokens. This is generally your public fully qualified domain with the https:// protocol prefix. For example, https://example.com.

The unique id of the signing key used to sign the access token.

The unique id of the signing key used to sign the Id token.

The Refresh Token expiration policy.

The possible values are:

• Fixed - the expiration is calculated from the time the token is issued.
• SlidingWindow - the expiration is calculated from the last time the token was used.
• SlidingWindowWithMaximumLifetime - the expiration is calculated from the last time the token was used, or until the maximumTimeToLiveInMinutes is reached.   Available since 1.46.0

The length of time specified in seconds that a one-time use token can be reused.

This value must be greater than 0 and less than 86400 which is equal to 24 hours. Setting this value to 0 effectively disables the grace period which means a one-time token may not be reused. For security reasons, you should keep this value as small as possible, and only increase past 0 to improve reliability for an asynchronous or clustered integration that may require a brief grace period.

Note that one-time use tokens refreshed within a grace period are not considered for revocation when tenant.jwtConfiguration.refreshTokenRevocationPolicy.onOneTimeTokenReuse is true. When a token is reused within the grace period the current token will be returned on the API response and the token will not be rotated.

When enabled, all of a user's refresh tokens will be revoked when a user action, such as locking an account based on a number of failed login attempts, prevents user login.

When enabled, all of a user's refresh tokens will be revoked when the user enables multi-factor authentication for the first time. This policy will not be applied when adding subsequent multi-factor methods to the user.

When enabled, if a one-time use refresh token is reused, the token will be revoked. This does not cause all refresh tokens to be revoked, only the reused token is revoked.

When enabled, all of a user's refresh tokens will be revoked when a user changes their password.

The maximum lifetime of a refresh token when using a refreshTokenExpirationPolicy of SlidingWindowWithMaximumLifetime.

The length of time in minutes a Refresh Token is valid from the time it was issued. Value must be greater than 0.

The refresh token usage policy. The following are valid values:

• Reusable - the token does not change after it was issued.
• OneTimeUse - the token value will be changed each time the token is used to refresh a JWT. The client must store the new value after each usage.

The length of time in seconds this JWT is valid from the time it was issued. Value must be greater than 0.

The Id of the lambda that will be invoked at the end of a successful login request in order to extend custom validation of a login request.

The Id of the lambda that will be invoked during logins, password changes, and MFA Status API calls to perform various validations to decide whether to challenge the user on one of their MFA methods.

The Id of a SCIM User Request Lambda that will be used to convert the SCIM Enterprise User request to a FusionAuth User.

The Id of a SCIM User Response Lambda that will be used to convert a FusionAuth Enterprise User to a SCIM Server response.

The Id of a SCIM Group Request Lambda that will be used to convert the SCIM Group request to a FusionAuth Group.

The Id of a SCIM GroupResponse Lambda that will be used to convert a FusionAuth Group to a SCIM Server response.

The Id of a SCIM User Request Lambda that will be used to convert the SCIM User request to a FusionAuth User.

The Id of a SCIM User Response Lambda that will be used to convert a FusionAuth User to a SCIM Server response.

The instant that the Tenant was last updated in the FusionAuth database.

Indicates whether to require an API key for the Login API when an applicationId is not provided. When an applicationId is provided to the Login API call, the application configuration will take precedence.

The logout redirect URL when sending the user's browser to the /oauth2/logout URI of the FusionAuth Front End. This value is only used when a logout URL is not defined in your Application.

The password maximum age in days. The number of days after which FusionAuth will require a user to change their password. Required when tenant.maximumPasswordAge.enabled is set to true.

Indicates that the maximum password age is enabled and being enforced.

The password minimum age in seconds. When enabled FusionAuth will not allow a password to be changed until it reaches this minimum age. Required when tenant.minimumPasswordAge.enabled is set to true.

Indicates that the minimum password age is enabled and being enforced.

The algorithm used by the TOTP authenticator. This value is HmacSHA1 and read only.

The length of the code generated by the TOTP. This value is 6 and read only.

When enabled, users may utilize an authenticator application to complete a multi-factor authentication request. This method uses TOTP (Time-Based One-Time Password) as defined in RFC 6238 and often uses an native mobile app such as Google Authenticator.

The time-step size in seconds. This value is 30 and read only.

When enabled, users may utilize an email address to complete a two-factor authentication request.

The Id of the email template that is used when notifying a user to complete a two-factor authentication request.

When enabled, users may utilize a mobile phone number to complete a two-factor authentication request.

The messenger that is used to deliver a SMS two-factor authentication request.

The Id of the SMS template that is used when notifying a user to complete a two-factor authentication request.

When enabled, users can receive a spoken multi-factor authentication code over a phone call.

The messenger that is used to deliver a voice two-factor authentication request.

The Id of the voice template that is used when notifying a user to complete a two-factor authentication request.

The unique name of the Tenant.

The Id of a lambda that will be called to populate the JWT during a client credentials grant.

The default method for encrypting the User's password. The following encryptors are provided with FusionAuth:

• salted-md5
• salted-sha256
• salted-hmac-sha256
• salted-pbkdf2-hmac-sha256
• salted-pbkdf2-hmac-sha256-512
• salted-pbkdf2-hmac-sha512-512
• bcrypt
• phpass-md5
• phpass-sha512

The factor used by the password encryption scheme. If not provided, the PasswordEncryptor provides a default value. Generally this will be used as an iteration count to generate the hash. The actual use of this value is up to the PasswordEncryptor implementation.

When enabled a user's hash configuration will be modified to match these configured settings. This can be useful to increase a password hash strength over time or upgrade imported users to a more secure encryption scheme after an initial import.

Beginning in version 1.42.0 when this configuration is enabled, in addition to re-hashing on login, the password will be re-hashed on password change as well.

Whether to enable Reactor breach detection. Requires an activated license.

The level of severity where Reactor will consider a breach. The following are valid values:

• High Only requires a password match, this is the most secure and is recommended
• Medium Exact match on username, email address or email sub-address
• Low Exact match on an email or username, or the password is a common breached value

The Id of the email template to use when notifying a user of a breached password.

The behavior when detecting breaches at time of user login. The following are valid values:

• Off Do not perform breach detection at login
• RecordOnly Only record the result, take no action
• NotifyUser Notify the end user via email
• RequireChange Require immediate password change

The maximum length of a password when a new user is created or a user requests a password change.

The minimum length of a password when a new user is created or a user requests a password change.

The number of previous passwords to remember. Value must be greater than 0.

Whether to prevent a user from using any of their previous passwords.

Whether to force the user to use at least one uppercase and one lowercase character.

Whether to force the user to use at least one non-alphanumeric character.

Whether to force the user to use at least one number.

When enabled the user's password will be validated during login. If the password does not meet the currently configured validation rules the user will be required to change their password.

The Id of the Message Template that is used when sending a user a forgot password message.

The Id of the Message Template used to send a message to a user when their phone number has been updated. The message will be sent to both their new and old phone numbers.

When set to true, this allows a phone number to be verified as a result of completing a similar phone based workflow such as change password. When set to false, the user must explicitly complete the phone verification workflow even if the user has already completed a similar phone workflow such as change password.

The Id of the Message Template used to send a message to a user when another user attempts to create an account with their login Id.

The Id of the Message Template used to send a message to a user when another user attempts to update an existing account to use their login Id.

The Id of the Message Template used to send a message to a user when they log in on a new device.

The Id of the Message Template used to send a message to a user when a suspicious login using their login Id occurs.

The messenger that is used to deliver SMS messages for phone number verification and passwordless logins.

The Id of the Passwordless Message Template, sent to users when they start a passwordless login.

The Id of the Message Template used to send a message to a user when they have completed a 'forgot password' workflow and their password has been reset.

The Id of the Message Template used to send a message to a user when their password has been updated.

The Id of the SMS Message Template used when a user must set their password manually after their account was created for them (by an admin, for example).

The Id of the Message Template used to notify a user when an administrator removes one of their MFA methods.

The Id of the Message Template used to send a message to a user when a MFA method has been removed from their account.

The Id of the Message Template used to send a message to a user when a MFA method has been added to their account.

When this value is set to true, the user is allowed to change their phone number when they are gated because they haven't verified their phone number.

The desired behavior during login for a user that does not have a verified phone number. The possible values are:

• Allow - the user will be allowed to complete login.
• Gated - verification is required before a user can complete login. The use of this value will require a paid plan.

The Id of the Message Template used to notify a user that their phone number has been verified.

The process by which the user will verify their phone number. The possible values are:

• ClickableLink - send the user a code with a clickable link.
• FormField - send the user a short code intended to be manually entered into a form field. This is only available when tenant.phoneConfiguration.unverified.behavior has the Gated value.

The Id of the Message Template used to send SMS messages to users to verify that their phone number is valid.

Whether a user's phone number is verified when they register with your application.

The number of times a user can fail to login within the configured timePeriodInSeconds duration. If a Failed authentication action has been configured then it will take precedence.

The duration for the number of times a user can fail login before being rate limited.

The number of times a user can request a forgot password email within the configured timePeriodInSeconds duration.

The duration for the number of times a user can request a forgot password email before being rate limited.

The number of times a user can request a verification email within the configured timePeriodInSeconds duration.

The duration for the number of times a user can request a verification email before being rate limited.

The number of times a user can request a passwordless login email within the configured timePeriodInSeconds duration.

The duration for the number of times a user can request a passwordless login email before being rate limited.

The number of times a user can request a passwordless login SMS message within the configured timePeriodInSeconds duration.

The duration for the number of times a user can request a passwordless login SMS message before being rate limited.

The number of times a user can request a phone verification message within the configured timePeriodInSeconds duration.

The duration for the number of times a user can request a phone verification message before being rate limited.

The number of times a user can request a registration verification email within the configured timePeriodInSeconds duration.

The duration for the number of times a user can request a registration verification email before being rate limited.

The number of times a user can request a two-factor code by email or SMS within the configured timePeriodInSeconds duration.

The duration for the number of times a user can request a two-factor code by email or SMS before being rate limited.

A list of unique domains that are not allowed to register when self service is enabled.

The Entity Type that will be used to represent SCIM Clients for this tenant.

Whether or not this tenant has the SCIM endpoints enabled.

JSON formatted as a SCIM Schemas endpoint response. Because the SCIM lambdas may modify the JSON response, ensure the Schema's response matches that generated by the response lambdas. More about Schema definitions.

The Entity Type that will be used to represent SCIM Servers for this tenant.

The number of seconds before a trusted device is reset. When reset, a user is forced to complete captcha during login and complete two-factor authentication if applicable.

When enabled, an SSO session can be created after login by providing an access token as a bearer token in a request to the OAuth2 Authorize endpoint.

The current state of the tenant. The following are valid values:

• Active - The tenant is active.
• PendingDelete - A delete request has been requested and is being processed.

The unique Id of the theme to be used to style the login page and other end user templates.

Indicates that users without a verified email address will be permanently deleted after tenant.userDeletePolicy.unverified.numberOfDaysToRetain days.

The instant that this policy was enabled.

Users created before this time will not be eligible to be deleted. This means that you can safely enable this feature and the policy will only be enforced for users created after this policy was enabled. If you would like to delete users created prior to this policy being enabled that have an unverified email address, you can use the User Search API or User Bulk Delete API to search on the insertInstant and verified fields to identify users that you would like to delete.

For example, the following query string will return users that were created at least 7 days ago that have not verified their email address.

insertInstant:<now-7d AND verified:false

Please note that prior to version 1.48.0, when enabling this policy all user's with an unverified email were eligible for deletion.

The number of days from creation users will be retained before being deleted for not completing email verification. Value must be greater than 0.

When true, FusionAuth will handle username collisions by generating a random suffix. Users with colliding usernames will be able to use the same one, but in the admin and API interfaces, a unique username will be displayed.

The maximum number of digits to use when building a unique suffix for a username. A number will be randomly selected and will be 1 or more digits up to this configured value in length. For example, if this value is 5, the suffix will be a number between 00001 and 99999, inclusive.

A single character to use as a separator from the requested username and a unique suffix that is added when a duplicate username is detected. This value can be a single non alphanumeric ASCII character.

This strategy instructions FusionAuth when to append a unique suffix to the username. The possible values are:

• Always - Always append a unique suffix even when the requested username is not in use.
• OnCollision - Only append a unique suffix when the requested username is in use.

The authenticator attachment requirement for WebAuthn passkey registration when using the bootstrap workflow. The possible values are:

• any - An authenticator with any attachment modality will be allowed during registration.
• crossPlatform - Only authenticators with the cross-platform attachment modality will be allowed during registration. These are also referred to as "roaming" authenticators.
• platform - Only authenticators with the platform attachment modality will be allowed during registration.

Whether the WebAuthn bootstrap workflow is enabled.

The user verification requirement for WebAuthn passkey registration and authentication when using the bootstrap workflow. The possible values are:

• discouraged - If possible, do not require user verification during registration and authentication.
• preferred - Prefer authenticators that support user verification during registration and authentication but allow others.
• required - Only authenticators that support user verification will be allowed.

Whether debug event log output is enabled for WebAuthn.

Whether WebAuthn configuration is enabled.

The authenticator attachment requirement for WebAuthn passkey registration when using the reauthentication workflow. The possible values are:

• any - An authenticator with any attachment modality will be allowed during registration.
• crossPlatform - Only authenticators with the cross-platform attachment modality will be allowed during registration. These are also referred to as "roaming" authenticators.
• platform - Only authenticators with the platform attachment modality will be allowed during registration.