On Wed, Nov 21, 2018 at 2:25 PM Nick Couchman <[email protected]> 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 > module and is checked against that module. I believe this works correctly > between, for example, LDAP -> JDBC (although I've never tried putting LDAP > authentication *after* JDBC), so I'm not sure why it isn't working for JDBC > -> RADIUS. >
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. - Mike
