Ok.... I'm having a senior moment. It looks like my server profile was
pointing to the wrong LDAP server (deprecated vs new)
Once it pointed to the new one, everything is fine in that it can see the
schemas that were not working.
Apologies and please close this issue.
Paul
On Monday, September 23, 2019, 8:54:39 AM EDT, Paul Pathiakis via
Lam-public <[email protected]> wrote:
Follow up:
CentOS 7.6
LAM 6.8
OpenLDAP 2.44
I have the loaded and configured the freeradius.schema and
freeradius-clients.schemaBoth of those schema exist and are in
/etc/openldap/schema and /etc/openldap/slapd.d
In the /etc/openldap/slapd.d/cn=config/cn=schema there are .ldif files for both
freeradii schema.
In the /etc/openldap/schema directory, I have checked the schema and found the
radiusprofile attribute exists.
Paul
On Monday, September 23, 2019, 8:14:50 AM EDT, Paul Pathiakis via
Lam-public <[email protected]> wrote:
Hi,
The subject says it all. I'm trying to enable the FreeRADIUS module and the
subsequent user module.
However, it tells me I can add that object class.
So, I go to Tools->Tests->Schemas and see the error in Subject line there.
What am I missing and how do I correct it?
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
_______________________________________________
Lam-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lam-public
