And now for the second, 'self-solved' issue today.
Looks like someone 'helped' me while I was off on Friday. It seems someone
configured the module and put a check on the 'enabled' but as they wanted it
enabled in every profile.... this performed the exact 'opposite' of what they
were trying to do. *sigh*
I am truly sorry for spamming the list today.
Paul
On Monday, September 23, 2019, 9:37:23 AM EDT, Paul Pathiakis via
Lam-public <[email protected]> wrote:
Hi,
OpenLDAP 2.44
CentOS 7.6
LAM 6.8
I have a strange issue in that I have the latest freeradius and
freeradius-client schemas now implemented in my new server.
I'm upgrading from LAM 5.4 and I noticed something on that version with the
FreeRADIUS extension versus the new.
There used to be an 'enabled' button and it no longer exists. Is that a change
in LAM or in the FreeRADIUS schemas?
It would seem useful to have it in that you may want to temporarily disable a
user account via the 'dialupAccess' attribute.
Could someone tell me what has happened to that attribute? Do they still see
it in the current version?
Did I miss something in it's removal in the RELEASE NOTES?
Thank you,
Paul
_______________________________________________
Lam-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lam-public
_______________________________________________
Lam-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lam-public
