NS8-Guacamole - first testing prerelease

Hi friends,

by using the ns8-kickstart-db templates by @stephdl I was finally able to create my first NS8 module.

If you like to test Guacamole on NS8:

add-module ghcr.io/mrmarkuz/guacamole:working

Just configure the guacamole hostname in the app settings page in cluster admin and browse to https://configured.hostname.tld/guacamole. The default login is user guacadmin, password guacadmin.

Backup/Restore should work already from the template.

Still on the todo list:

  • LDAP/AD bind
  • Branding
  • Remove guacamole path in URL
8 Likes

I am happy :slight_smile:

2 Likes

Congratulations on your first Module @mrmarkuz

I am also very interested in learning how the AD/Ldap Integrations works.

Managed to install successfully, the module is reachable at /guacamole

username and password guacadmin/guacadmin

1 Like

is this not all i need to conenct to a server


I keep getting this
image

Woooooooooow
Looks like FOSDEM you did well.
Good job my friend!

@stephdl you have a new promising padawan! :smiley:

I would move it to Development testing and create a new topic once it is released. What do you think @mrmarkuz ?

2 Likes

How to remove the module? (My case 1 node cluster). I tried this:

[root@srv1 ~]# remove-module guacamole:working
<3>Cannot retrieve the NODE_ID of guacamole:working

[root@srv1 ~]# remove-module guacamole
<3>Cannot retrieve the NODE_ID of guacamole

[root@srv1 ~]# remove-module --help
usage: remove-module [-h] [–no-preserve] [–force] module

positional arguments:
module

options:
-h, --help show this help message and exit
–no-preserve erase also the module home directory
–force unconditionally erase the module from Redis (dangerous)
[root@srv1 ~]#

Reason for removal is that no ldap domains are listed in the settings page.

HTH

remove-module guacamole1

LDAP isn’t implemented yet


1 Like

Ah, my bad in bad reading :wink:

Anyway, the issue is the following:

  • Installed the module (add-module)
  • Entered the settings FQDN, certificate and HTTPS
  • Save setting
  • go to FQDN entered in settings

Do you really need help to do a simple SSH connection to a server?

All current OS have. a usable SSH client nowadays, even Windows!
Why would any sane person waste more than one persons time trying to run SSH over HTML5 when every OS has SSH?

A Desktop is a different matter, the encryption for any Desktoptransfer with VNC or RDP is not enough, so a VPN is needed. Guacamole makes setting up a VPN redundant.

My 2 cents
Andy

1 Like

i think this will preseve some data,

remove-module --no-preserve guacamole1

for complete removal

1 Like

Using Guacamole, YEs Andy i actually need help, thats why i posted.

Thanks @oneitonitram !

[root@srv1 ~]# remove-module --no-preserve guacamole1

<7>podman rmi --ignore 1238c5206383fd1e698aaa63f8b0ed18efbec1926cf376e511849eaf07d46419

Untagged: Package guacamole · GitHub

Deleted: 1238c5206383fd1e698aaa63f8b0ed18efbec1926cf376e511849eaf07d46419

{}

[root@srv1 ~]#

1 Like

Looks like you missed the /guacamole path

1 Like

Ok, let me try again. BUT, I rather have immediate access through the given FQDN without a trailing directory. Just like the Sterling PDF module of @oneitonitram. Simply go to the dedicated subdomain. Very user friendly for for the end user spelling and remembering ‘guacamole’ is a nightmare and has nothing to do with what they want.

They simply want their desktop, hence e.g. https://mypc.mydomain.com :slight_smile:

1 Like

It’s on the todo list:

4 Likes

I need to RTFM!!

It works as advertised! Thanks!

2 Likes

Please test the brand new Guacamole 1.5.5 app!

The open points were finished:

The LDAP/AD bind is optional.

To be able to install via Software Center you can add my repo.

Installation from CLI:

add-module ghcr.io/mrmarkuz/guacamole:1.0.0-beta.2

Removal:

remove-module --no-preserve guacamole1

Documentation is on GitHub.

5 Likes

That is WAY cool!

And works!

And that has been ‘fixed’ too! Very clean URL now. No more “kwakomoloo” typos!

4 Likes

this sounds like an african dialect

@mrmarkuz i dont think you have defined the administrative user while using ldap.

seems guacadmin is still able to login as the defacto admin
under users, i dont see the ldap users, even though they have already loggedin before.

Am i missing something?

1 Like

Thanks for testing, guys!

You need to give permissions to the ldap users, one method is to create a “domain admins” group as guacadmin, so every LDAP domain admin can login and sees all users/groups.

You can delete the guacadmin user, if you don’t like it to login anymore but it’s a good fallback if LDAP isn’t working.

LDAP is only used for auth, the permissions are stored in postgresql, it was the same for Guacamole in NS7.

It’s documented here.

3 Likes