Thanks for reply.

> This is already covered in the manual - the section you mentioned in the JDBC 
> chapter of the manual contains instructions for each of the databases (MySQL, 
> Postgres, and SQL Server) for creating a user and granting that user access 
> to the database.

In my opinion, the documentation is a bit unclear in this point. For people 
which don’t have to do with DBs often, the documentation should be clarified 
that some queries should be done on the postgres system db and some on the 
newly created guacamole_db. Now, that I know that it should be done this way, 
it totally makes sense, but like I said, this is not easy to identify for some 
people.

>There is nothing wrong with the code in the git repository - you are using a 
>link to a specific tag for the 0.9.10-incubating version of Guacamole, which 
>is, indeed, very old. You should either use the SQL Scripts included in the 
>JDBC download for the version of Guacamole you're running, or use the SQL file 
>produced by running the initdb script. Please note, running the initdb script 
>does not actually initialize the database, it just produces a .sql file that 
>you can then use as the input for either mysql or psql commands to initialize 
>the database yourself.

Yes, I found the link on the official guacamole docker pager under postgres and 
mysql. One of the maintainers should update both links please. Maybe to a 
point, where you can always find the latest version, not a specific one. See: 
https://hub.docker.com/u/guacamole



-----Ursprüngliche Nachricht-----
Von: Nick Couchman <[email protected]> 
Gesendet: Donnerstag, 2. März 2023 14:26
An: [email protected]
Betreff: Re: Guacamole 1.5.0 not working in docker

On Thu, Mar 2, 2023 at 7:01 AM Fischer, Manuel 
<[email protected]> wrote:
>
> Its working now. I found the reason. In postgres, you have to do the
>
> CREATE USER guacamole_user WITH PASSWORD 'some_password';
>
> on the postgres DB (all users and permissions are located in this DB) 
> and
>
> GRANT SELECT,INSERT,UPDATE,DELETE ON ALL TABLES IN SCHEMA public TO 
> guacamole_user; GRANT SELECT,USAGE ON ALL SEQUENCES IN SCHEMA public 
> TO guacamole_user;
>
> on the guacamole_db DB.
>
>
> This is not properly described in the guacamole documentation:
> http://guacamole.incubator.apache.org/doc/gug/jdbc-auth.html#jdbc-auth
> -mysql

Yes, it is - from the page you mentioned (though you're using an old link), if 
you click on the PostgreSQL tab, you'll see the following:

psql -d guacamole_db
psql (9.3.6)
Type "help" for help.

guacamole=# CREATE USER guacamole_user WITH PASSWORD 'some_password'; CREATE 
ROLE guacamole=# GRANT SELECT,INSERT,UPDATE,DELETE ON ALL TABLES IN SCHEMA 
public TO guacamole_user; GRANT guacamole=# GRANT SELECT,USAGE ON ALL SEQUENCES 
IN SCHEMA public TO guacamole_user; GRANT guacamole=# \q

>
>
> Are here some guacamole devs who can:
>
> 1. update the sql scripts on the github link (see belowe)?

There is nothing wrong with the code in the git repository - you are using a 
link to a specific tag for the 0.9.10-incubating version of Guacamole, which 
is, indeed, very old. You should either use the SQL Scripts included in the 
JDBC download for the version of Guacamole you're running, or use the SQL file 
produced by running the initdb script. Please note, running the initdb script 
does not actually initialize the database, it just produces a .sql file that 
you can then use as the input for either mysql or psql commands to initialize 
the database yourself.

>
> 2. update the "Granting Gutacamole access to the database" part so that you 
> have to create the user on the postgres db and the access rights on the 
> guacamole_db?
>

This is already covered in the manual - the section you mentioned in the JDBC 
chapter of the manual contains instructions for each of the databases (MySQL, 
Postgres, and SQL Server) for creating a user and granting that user access to 
the database.

-Nick

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to