This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Weak password of 96 characters ?

Hello,

 

We created a security administrator to test (all roles).  Although the account is created with a password generator, 96 characters, maximum complexity the system reports : 

Are we doing something wrong please ? We are running SFOS 16.05.1 MR-1

 

Thanks !




[locked by: FloSupport at 12:53 AM (GMT -7) on 24 Apr 2019]
Parents
  • Hi KoenT,

    Show me a picture from Administration | Admin Settings | Administrator Password Complexity Settings. 

    Thanks

  • I think these are the default settings.

  • Hi Koen, 

    The default is disabled. I tested it on my test appliance, seems no issue. Make sure you have changed the default admin password to comply with the conditions in Administration | Device Access | Admin Password.

    Note: XG will not allow a password that does not fulfill the conditions checked in the password complexity settings. Whenever a weak password is used they will receive an error:

    Thanks

  • I'm sorry, but it seems I created some confusion.

    With 'default ', I refered to the password complexity settings.

    The password I put on the admin account is more than compliant with the complexity settings but I still receive an error message on the dashboard that the administrator account  is not safe.

  • KoenT,

    I am also having this problem in SFOS 16.05.6 MR-6.  From trial and error I discovered that both of the following Password Complexity Checks work, but give a report that is incorrect. In Administartion/Admin Settings, under the Administrator Password Complexity Settings section:

     - Include at least 1 upper-case and 1 lower-case alphabetic character

     - Include at least 1 special character like '@', '$', '!', etc

    If you check all of the Password Complexity Checks, when you change a administrator's password, it will not allow you to create a password that doesn't meet the criteria (so the complexity checks work in that regard), HOWEVER, you will now receive an alert that says "Some of the administrators have a weak password that does not conform to the password complexity settings. To change their password, Click Here", even thought the password DOES meet the criteria!

    Clearly the password passed criteria, or it would not allow you to implement it.  Even with the same password, if you uncheck the 2 options listed above, the alert goes away.  If you check them again, the alert reappears.  Updating the password to another one that also meets the criteria also give the same alert.  It appears the alerting system is incorrect.

    You might just suggest unchecking those two options to make the alert go away, but now you can enter a password that doesn't meet those criteria.  (i.e. 12345678 works if the length is set to 8).

    Until this bug is fixed, you can either leave those settings off, or learn to live with the alert that will never go away.

Reply
  • KoenT,

    I am also having this problem in SFOS 16.05.6 MR-6.  From trial and error I discovered that both of the following Password Complexity Checks work, but give a report that is incorrect. In Administartion/Admin Settings, under the Administrator Password Complexity Settings section:

     - Include at least 1 upper-case and 1 lower-case alphabetic character

     - Include at least 1 special character like '@', '$', '!', etc

    If you check all of the Password Complexity Checks, when you change a administrator's password, it will not allow you to create a password that doesn't meet the criteria (so the complexity checks work in that regard), HOWEVER, you will now receive an alert that says "Some of the administrators have a weak password that does not conform to the password complexity settings. To change their password, Click Here", even thought the password DOES meet the criteria!

    Clearly the password passed criteria, or it would not allow you to implement it.  Even with the same password, if you uncheck the 2 options listed above, the alert goes away.  If you check them again, the alert reappears.  Updating the password to another one that also meets the criteria also give the same alert.  It appears the alerting system is incorrect.

    You might just suggest unchecking those two options to make the alert go away, but now you can enter a password that doesn't meet those criteria.  (i.e. 12345678 works if the length is set to 8).

    Until this bug is fixed, you can either leave those settings off, or learn to live with the alert that will never go away.

Children