>
> In the JDBC -> RADIUS case where it's not working as expected, what
> exceptions are thrown during the authentication process? It might help
> to step through the auth process with a debugger to see what throws
> what and when.
>
>
I've pasted the contents of the log file from the
On Wed, Nov 21, 2018 at 2:25 PM Nick Couchman wrote:
> ...
> That authentication of that user moves through each of the modules. So, if
> the JDBC module fails, either because the user is not present in JDBC or is
> present but password does not match, authentication moves on to the RADIUS
>
On Wed, Nov 21, 2018 at 3:52 AM Mike Jumper wrote:
> On Tue, Nov 20, 2018 at 10:46 AM Nick Couchman
> wrote:
>
> > Hey, everyone,
> > Ran back into an issue with the RADIUS module that I thought was
> resolved a
> > while back, but seems to have re-appeared. In my current testing, I'm
> >
On Tue, Nov 20, 2018 at 10:46 AM Nick Couchman
wrote:
> Hey, everyone,
> Ran back into an issue with the RADIUS module that I thought was resolved a
> while back, but seems to have re-appeared. In my current testing, I'm
> using both RADIUS and JDBC PostgreSQL for authentication. Guacamole
Hey, everyone,
Ran back into an issue with the RADIUS module that I thought was resolved a
while back, but seems to have re-appeared. In my current testing, I'm
using both RADIUS and JDBC PostgreSQL for authentication. Guacamole loads
and evaluates authentication against each of the extensions
