Understanding our password requirements
Overview
To protect your account, DroneDeploy enforces specific password requirements to ensure your credentials are strong and secure. This guide outlines the rules your password must follow. When you create or change your password, the system automatically checks it against these requirements.
Password requirements
Your password must meet the following criteria to be accepted.
Length requirements
- Minimum length: 12 characters
- Maximum length: 50 characters
Content restrictions
Your password must not include:
- The word "password" (in any case)
- Company-related words, such as "drone", "dronedeploy", or "structionsite"
- Your full email local-part (the text before the @ symbol)
- Your email domain name (the text after the @ symbol)
Pattern restrictions
Your password must not contain:
- The same character repeated 4 or more times in a row (for example, "aaaa" or "1111")
- Four or more sequential characters, such as:
- Forward alphabetical sequences (for example, "abcd")
- Reverse alphabetical sequences (for example, "dcba")
- Forward numerical sequences (for example, "1234")
- Reverse numerical sequences (for example, "4321")
Common password checks
When you create or change a password, the system checks it against a list of approximately 1,000,000 common and easily guessed passwords. If your chosen password is on this list, it will be rejected, and you will see an error message: "Your password is too weak or easy to guess. Please choose a stronger password."
This list includes:
- Simple passwords like "123456" and "admin"
- Popular passwords taken from security breach databases
- Company-specific terms like "drone" and "dronedeploy"
- Sequential patterns like "abcd" and "1234"
Technical implementation details
- Password validation is not case-sensitive and is normalized to lowercase.
- Diacritics (such as é or ü) are removed during validation.
- Validation occurs on the client-side and through the
PasswordValidation.strongPassword()method. - Error messages are displayed in a priority order, starting with length and then moving to content restrictions.
v2.2