Skip to content

limit accepted message passwords based on password policy #1618

Closed

Description

@tomholub

part of #1545

Activity

  1. changed the title [-]limit accepted passwords based on password policy - will share[/-] [+]limit accepted message passwords based on password policy - will share[/+] on Dec 20, 2021
  2. tomholub commented on Dec 20, 2021

    @tomholub
    CollaboratorAuthor

    We'll need a method that will validate user message passwords to make sure it complies with password policy. I'll share the policy separately (not public).

  3. self-assigned this
    on Dec 20, 2021
  4. DenBond7 commented on Jan 6, 2022

    @DenBond7
    Collaborator

    @tomholub Any news here?

  5. tomholub commented on Jan 6, 2022

    @tomholub
    CollaboratorAuthor

    Sorry, it's stuck on me.

  6. DenBond7 commented on Jan 6, 2022

    @DenBond7
    Collaborator

    Don't worry. I'm going to work on #1620

  7. tomholub commented on Jan 13, 2022

    @tomholub
    CollaboratorAuthor

    when using FES to send the password protected message, use the following password rules:

    • minimum one uppercase
    • minimum one lowercase
    • minimum one number
    • minimum one special character such as eg &"#-'_-@,;!*()[] etc
    • minimum length 8 characters
  8. tomholub commented on Jan 13, 2022

    @tomholub
    CollaboratorAuthor

    The implementation can check for all of these rules at once and when not conforming, show:

    Password didn't comply with company policy, which requires at least:
    
     - one uppercase
     - one lowercase
     - one number
     - one special character eg &"#-'_%-@,;:!*()
     - 8 characters length
    
    Please update the password and re-send.
    
  9. changed the title [-]limit accepted message passwords based on password policy - will share[/-] [+]limit accepted message passwords based on password policy[/+] on Jan 13, 2022
  10. 11 remaining items

  11. DenBond7 commented on Jan 22, 2022

    @DenBond7
    Collaborator

    so either there is nothing or a standalone checkmark, that would be a bit better.

    @tomholub Looks better?
    image

    image

    image

  12. tomholub commented on Jan 22, 2022

    @tomholub
    CollaboratorAuthor

    Sure. Less pretty but also less confusing :-)

    Two things I noticed:

    • The bottom red text can be gray like the rest of the text.
    • Also in FES situations it should say They will have access to this message for 180 days.
  13. DenBond7 commented on Jan 22, 2022

    @DenBond7
    Collaborator

    image

  14. tomholub commented on Jan 22, 2022

    @tomholub
    CollaboratorAuthor

    yup

  15. IvanPizhenko commented on Jan 22, 2022

    @IvanPizhenko
    Contributor

    put "min 8 characters" on top of the list

  16. DenBond7 commented on Jan 22, 2022

    @DenBond7
    Collaborator

    tests

    • hide "Tap to protect..." button when message type == standard
    • test password strength (show checkboxes and etc.)
    • test button 'enable" state
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions