You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by Dino Edwards <di...@mydirectmail.net.INVALID> on 2021/12/14 15:47:15 UTC

Guacamole on Docker, Postgresql The authentication type 10 is not supported.

When trying to launch Guacamole on Docker using postgresql, we get the following error:

The authentication type 10 is not supported

Looking at the following Guacamole Jira issue, it indicates that it has been Resolved:

https://issues.apache.org/jira/browse/GUACAMOLE-1433

However, this does not seem to be the case because pulling the latest Guacamole image  still has the same error. The only way to get around this issue is to edit the pg_hba.conf and set the following line:

host      all          all          scram-sha-256

to

host      all          all          trust

and the error goes away.

Am I missing something here or has the fix not trickled to the latest Guacamole image?

Thanks



Re: Guacamole on Docker, Postgresql The authentication type 10 is not supported.

Posted by Nick Couchman <vn...@apache.org>.
On Tue, Dec 14, 2021 at 10:47 AM Dino Edwards
<di...@mydirectmail.net.invalid> wrote:

> When trying to launch Guacamole on Docker using postgresql, we get the
> following error:
>
>
>
> *The authentication type 10 is not supported*
>
>
>
> Looking at the following Guacamole Jira issue, it indicates that it has
> been Resolved:
>
>
>
> https://issues.apache.org/jira/browse/GUACAMOLE-1433
>
>
>
> However, this does not seem to be the case because pulling the latest
> Guacamole image  still has the same error. The only way to get around this
> issue is to edit the pg_hba.conf and set the following line:
>
>
>
> *host      all          all          scram-sha-256 *
>
>
>
> to
>
>
>
> *host      all          all          trust*
>
>
>
> and the error goes away.
>
>
>
> Am I missing something here or has the fix not trickled to the latest
> Guacamole image?
>
>
>

It has been resolved, but only in the git repo - we have not released the
version where it is resolved. That's actually slated for version 1.5.0,
which is our placeholder for whatever comes after 1.4.0 - the next release.

-Nick

>