The answer is in the packetfence.log file.
Paste it when you connect.
Le lun. 31 oct. 2022, 18 h 23, Alexander a
écrit :
> thank you very much! I achieved what was described by changing the base
> config. i Get* [mschap] = ok. * But I am now getting a different error!
> Could you see the file at
thank you very much! I achieved what was described by changing the base
config. i Get* [mschap] = ok. * But I am now getting a different error!
Could you see the file attachment?
(0) mschap: Found NT-Password
(0) mschap: Client is using MS-CHAPv1 with NT-Password
(0) mschap: adding MS-CHAPv1 MPPE
Hello Alexander,
the difference is on the default radius config, it calls the ldap module in
the authorize section.
You can follow this logic in
https://github.com/inverse-inc/packetfence/tree/devel/addons/nthash_AD_attribute
(it´s based on freeradius 2 but the logic is there)
```
authorize {
Hello friends! I need help
i am testing *local installed freeradius* configuration to work with
freeipa (ldap) on nthash via mschap-v2
what did i do for this:
1) yum install freeradius-ldap
2) ln -s /etc/raddb/mods-available/ldap /etc/raddb/mods-enabled/ldap
3) change /etc/raddb/mods-available/l
Yes.. google ldap is just a setting under google's workspace.
I committed some additional documentation to PF's google ldap /
documentation here (its not in the public builds yet)
https://github.com/inverse-inc/packetfence/blob/devel/docs/installation/google_workspace_ldap.asciidoc
You need to e