Hi Stephan,
I´d agree if authentication were the only goal of the API. However it also
allows to authorize users, and to provide (including create) configuration data
entirely not in the standard database. I visualized that capability and how I
use it in
https://software.lindenberg.one/backup/e
Hi,
On 21/04/2024 06:47, My Data Belongs to Me! wrote:
Hello,
I am running Alma 8, and followed the these instructions to get Guacamole
installed and running:
https://guacamole.apache.org/doc/gug/installing-guacamole.html
when things were not working (guacd would run and exit, tomcat would not
Hello,
I am running Alma 8, and followed the these instructions to get Guacamole
installed and running:
https://guacamole.apache.org/doc/gug/installing-guacamole.html
when things were not working (guacd would run and exit, tomcat would not unpack
any wars at all), I then reviewed these
https://id
>
> Hello Nick,
>
> first of all, thank you for looking into the issue. So please let me ask
> this
> as a real question and no offence.
>
None taken, perfectly fine to ask this.
> Why does the project _at all_ use a rather complicated API for
> authentication
> instead of "outsourcing" the func
Robert,
You might want to look to the links that Nick posted, they will give you
an idea of where progress is on this matter.
Also, you are always welcome to contribute, particularly if there's an
issue you see would assist the project as a whole in addition to your
operation.
On 21/04/24
On Sat, 20 Apr 2024 15:52:58 -0400
Nick Couchman wrote:
> >
> >
> > > I believe the issue that Stephan is describing is that, when the user
> > logs
> > > in to Guacamole, and the remote LDAP server that is authenticating the
> > user
> > > logs a client IP address, it should log the IP
>
>
> > I believe the issue that Stephan is describing is that, when the user
> logs
> > in to Guacamole, and the remote LDAP server that is authenticating the
> user
> > logs a client IP address, it should log the IP address of the browser
> (far
> > end client) and not the IP address of the Guaca
It is six years old, in computer terms this is stone age. As one who
usually maintains the current distro on my servers apps with old requirements
are a PITA, especially pitted against other apps that only work with the latest
and perhaps not always greatest.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
On Sat, Apr 20, 2024 at 7:14 AM Robert Dinse
wrote:
>
> Really should port to the most recent since other projects may not
> remain
> in the stone age.
>
1. "Stone age" is not a fair assessment - Tomcat 9 is still actively
maintained with current releases (April 16, 2024 was the latest - 9
Really should port to the most recent since other projects may not remain
in the stone age.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not tele
On 20/04/2024 10:25, Alessandro Sironi wrote:
Hi,
Tomcat 10 is the issue, ti is not supported, you can go with T9 or T8
Regards,
Alessandro
Ouch.. I was not careful on the requirements. THank you.
With tomcat9, it's working.
--
Willy Manga
-
11 matches
Mail list logo