You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@guacamole.apache.org by mike-jumper <gi...@git.apache.org> on 2017/01/05 21:55:18 UTC

[GitHub] incubator-guacamole-manual pull request #22: GUACAMOLE-36: Document password...

GitHub user mike-jumper opened a pull request:

    https://github.com/apache/incubator-guacamole-manual/pull/22

    GUACAMOLE-36: Document password policy usage and schema

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mike-jumper/incubator-guacamole-manual password-policies

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-guacamole-manual/pull/22.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #22
    
----
commit 79ada4523ef0feec914e0d2f93e11d79415163a8
Author: Michael Jumper <mj...@apache.org>
Date:   2016-08-23T18:03:13Z

    GUACAMOLE-36: Document password policy changes to JDBC auth schema.

commit b76c7f591be21587c0d4c5fad64178a71f43d8a2
Author: Michael Jumper <mj...@apache.org>
Date:   2016-08-23T19:11:33Z

    GUACAMOLE-36: Document JDBC auth's password policy properties.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-guacamole-manual pull request #22: GUACAMOLE-36: Document password...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/incubator-guacamole-manual/pull/22


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---