Cache user access on eap-ttls with ldap as authenticate system
André
netriver at gmail.com
Thu Jan 14 18:00:50 CET 2021
Hello,
This only caches ldap attributes, it's not able to store results
Access-Accept for example from a existing ldap confirmed authentication?
Would it be possible to store the result "Access-Accept" for a user +
password combination for future approval?
Best regards,
On Thu, Jan 14, 2021 at 3:54 PM Alan DeKok <aland at deployingradius.com>
wrote:
>
>
> > On Jan 14, 2021, at 10:45 AM, André <netriver at gmail.com> wrote:
> >
> > I did remove the inner-tunnel and it worked.
>
> I have no idea what that means.
>
> You edited sites-enabled/default. I was trying to tell you that the
> code block you posted should go into the sites-enabled/inner-tunnel file.
>
> If you deleted the inner-tunnel virtual server, then EAP won't work
> without many other changes.
>
> > But I could not see where you found inner-tunnel
>
> In the default configuration. It works. The more you edit it, the more
> likely it is that you'll break something.
>
> Start with the default configuration. Configure the LDAP module. Then
> add the cache code you posted to the list to the sites-enabled/inner-tunnel
> virtual server.
>
> Alan DeKok.
>
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
More information about the Freeradius-Users
mailing list