Security Settings
The options in the security section allows you to configure all things security, whether to keep users logged in, password rules and more.
A full configuration with all default values can be seen here:
"Umbraco": {
"CMS": {
"Security": {
"KeepUserLoggedIn": false,
"HideDisabledUsersInBackOffice": false,
"AllowPasswordReset": true,
"AuthCookieName": "UMB_UCONTEXT",
"AuthCookieDomain": "",
"UsernameIsEmail": true,
"UserPassword": {
"RequiredLength": 10,
"RequireNonLetterOrDigit": false,
"RequireDigit": false,
"RequireLowercase": false,
"RequireUppercase": false,
"HashAlgorithmType": "PBKDF2.ASPNETCORE.V3",
"MaxFailedAccessAttemptsBeforeLockout": 5
},
"MemberPassword": {
"RequiredLength": 10,
"RequireNonLetterOrDigit": false,
"RequireDigit": false,
"RequireLowercase": false,
"RequireUppercase": false,
"HashAlgorithmType": "PBKDF2.ASPNETCORE.V3",
"MaxFailedAccessAttemptsBeforeLockout": 5
}
}
}
}
Root level settings
At the root level of security you can configure the following
Keep user logged in
If set to false a user will be logged out after a specific amount of time has passed with no activity, you can specify this time span in the global settings with the TimeOut
key.
Hide disabled users in backoffice
If this is set to "true" it's not possible to see disabled users, which means it's not possible to re-enable their access to the backoffice again. It also means you can't create an identical username if the user was disabled by a mistake.
Allow password reset
The feature to allow users to reset their passwords if they have forgotten them. By default, this is enabled but if you'd prefer to not allow users to do this it can be disabled at both the UI and API level by setting this value to "false".
Auth cookie name
The authentication cookie which is set in the browser when a backoffice user logs in, and defaults to UMB_UCONTEXT
.
Auth cookie domain
The authentication cookie which is set in the browser when a backoffice user logs in is automatically set to the current domain.
Username is email
This setting specifies whether the username and email address are separate fields in the backoffice editor. When set to "false", you can specify an email address and username, only the username can be used to log on. When set to "true" (the default value) the username is hidden and always the same as the email address.
User password settings
This section lets you define the password rules for users.
Required length
Specifies the minimum length a user password is allowed to be.
Require non letter or digit
Requires a users password to contain at least one character which is not a letter or a digit if enabled.
Require digit
Requires a users password to contain at least one digit if enabled.
Require lowercase
Requires a users password to contain at least on lowercase letter if enabled.
Max failed access attempts before lockout
Specifies the max amount of failed password attempts is allowed before the user is locked out of the site.
Hash algorithm type
Allows you to specify what hashing algorithm should be used to store the users password.
Options are:
"PBKDF2.ASPNETCORE.V3"
"PBKDF2.ASPNETCORE.V2"
"HMACSHA256"
"HMACSHA1"
Member password settings
This section allows you to define the password rules for members. This section is identical to the one for users.