[
https://issues.apache.org/jira/browse/GUACAMOLE-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300817#comment-15300817
]
Michael Jumper edited comment on GUACAMOLE-36 at 5/25/16 8:43 PM:
------------------------------------------------------------------
*NOTE:* I am tasked with beginning work on this very shortly via downstream
issue [GUAC-1546|https://glyptodon.org/jira/browse/GUAC-1546].
was (Author: mike.jumper):
*NOTE:* I tasked with beginning work on this very shortly via downstream issue
[GUAC-1546|https://glyptodon.org/jira/browse/GUAC-1546].
> Add support for password policies
> ---------------------------------
>
> Key: GUACAMOLE-36
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-36
> Project: Guacamole
> Issue Type: New Feature
> Components: guacamole-auth-jdbc
> Reporter: Michael Jumper
>
> Guacamole currently lacks support for enforcement of password policies within
> the existing authentication backends. This is not relevant for the backends
> which are read-only, but definitely makes a difference for the database
> authentication.
> We should provide password policies in line with current de facto standards.
> Specifically, the following restrictions need to be supported:
> # Minimum password age (how long before the password CAN be changed)
> # Maximum password age (how long before the password MUST be changed)
> # Minimum password length
> # Minimum number of character classes:
> ## Uppercase
> ## Lowercase
> ## Symbols
> ## Digits
> # Must not containing the username
> # Must not match last N passwords
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
