You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To mitigate the risk of easily guessed passwords facilitating unauthorized access there are two solutions: introduce additional authentication controls (i.e. two-factor authentication) or introduce a strong password policy. The simplest and cheapest of these is the introduction of a strong password policy that ensures password length, complexity, reuse and aging.
A strong password must be at least 8 characters long.
It should not contain any of your personal informationspecifically your real name, username, or even your company name.
It must be uniquefrom your previously used passwords.
It should not contain any word spelled completely.
It should contain characters from the four primary categories, including: uppercase letters, lowercase letters, numbers, and characters
Actual behaviour
There is no validation at all .
Steps to reproduce the behavior
Login with any user from Stratos Dashboard.
Go to top right hand side -> click on My profile -> edit userinfo
Enter the new password and save it .
Log output covering before error and any error statements
Insert log hereCopy
Detailed Description
There is no validation check on this new password field. User can able to put anything , of any length and with any character (and saved as well).
Context
Possible Implementation
The text was updated successfully, but these errors were encountered:
Stratos Version
Stratos 4.4.0
Frontend Deployment type
Backend (Jet Stream) Deployment type
Expected behaviour
To mitigate the risk of easily guessed passwords facilitating unauthorized access there are two solutions: introduce additional authentication controls (i.e. two-factor authentication) or introduce a strong password policy. The simplest and cheapest of these is the introduction of a strong password policy that ensures password length, complexity, reuse and aging.
Actual behaviour
There is no validation at all .
Steps to reproduce the behavior
Log output covering before error and any error statements
Detailed Description
There is no validation check on this new password field. User can able to put anything , of any length and with any character (and saved as well).
Context
Possible Implementation
The text was updated successfully, but these errors were encountered: