Actually, support for SHA-256 has recently been added: https://issues.apache.org/jira/browse/GUACAMOLE-1391 https://github.com/apache/guacamole-client/pull/633 https://github.com/apache/guacamole-client/pull/634
That said, the user-mapping.xml file is not really designed to scale for anything beyond either very simple use-cases (personal use in a home environment or something like that, or proving out functionality of Guacamole). If you're going to deploy it, use either LDAP or JDBC to store connection information, map users and groups, etc. -Nick On Thu, Aug 19, 2021 at 10:57 AM Craig Sawyer <[email protected]> wrote: > no, there are other auth methods however, such as LDAP, etc. see: > https://guacamole.apache.org/doc/gug/users-guide.html > > We use HTTP header auth, and have NGINX handle the authentication for > us. But I imagine lots of deployments use LDAP/AD auth. > > -Craig > > On Thu, Aug 19, 2021 at 5:00 AM Paula Carboné <[email protected]> > wrote: > > > > Hi, regarding the following lines of the user-mapping.xml file: > > > > <authorize > > username="guacadmin" > > password="96080775c113b0e5c3e32bdd26214aec" > > encoding="md5"> > > > > Is it possible to use a different encoding (apart from MD5) for the > password? I have tried with sha256 and sha512 but it does not seem to work. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
