Skip to main content

PasswordSettingsDto

The password policy of the portal, with the expressions a client can check a password against.

NameTypeDescriptionNotes
minLengthInteger (int32)The shortest password the portal accepts, 8 characters on a portal nobody has configured. Whatever the policy says, a password longer than 30 characters is refused as well, and that ceiling is not reported here.[required] [example: 8]
upperCaseBooleanWhether at least one uppercase letter is demanded. While it is false an uppercase letter is still allowed - the flag adds a requirement rather than permission.[required] [example: true]
digitsBooleanWhether at least one digit is demanded, read the same way as upperCase.[required] [example: true]
specSymbolsBooleanWhether at least one special symbol is demanded, read the same way as upperCase. Which symbols count is spelled out by specSymbolsRegexStr.[required] [example: false]
allowedCharactersRegexStrStringThe expression the whole password has to match, which is what defines the alphabet the portal accepts at all. It comes from the installation's configuration rather than from the portal policy, so it is the same for every portal of an installation and unaffected by the flags above.[required] [example: ^[a-zA-Z0-9!@#$%^&*()]+$] [nullable]
digitsRegexStrStringThe look-ahead expression that tests the digit requirement, meant to be applied only while digits is true. It is always filled in, so its presence is not itself a requirement.[required] [example: (?=.*\\d)] [nullable]
upperCaseRegexStrStringThe look-ahead expression that tests the uppercase requirement, to be applied while upperCase is true.[required] [example: (?=.*[A-Z])] [nullable]
specSymbolsRegexStrStringThe look-ahead expression that tests the special-symbol requirement, to be applied while specSymbols is true. It also enumerates the symbols the portal treats as special.[required] [example: (?=.*[!@#$%^&*()])] [nullable]