Hi Alan, Thanks for the hint. He directed me in the right direction ;-) I had the following in the authenticate section: authenticate { horizon_pam } Now according to your note I finally found the error and with the following change it works now synonymous. authenticate { Auth-Type PAM { horizon_pam } } Thanks again and nice greeting Lars __ Fachhochschule Dortmund University of Applied Sciences and Arts Dipl.-Ing. (FH) Lars Hillebrand Dez. VI, IT-Basisdienste Sonnenstraße 100 - 44139 Dortmund Raum SON D 008 Tel 0231 9112-253 Fax 0231 9112-338 lars.hillebrand@fh-dortmund.de <mailto:lars.hillebrand@fh-dortmund.de> www.fh-dortmund.de <http://www.fh-dortmund.de/>
Am 18.04.2017 um 15:37 schrieb Alan DeKok <aland@deployingradius.com>:
On Apr 18, 2017, at 7:01 AM, Lars Hillebrand <lars.hillebrand@fh-dortmund.de> wrote:
Is there a way to include multiple instances of the pam module in the radius?
Yes.
- Content of /etc/freeradius/modules/pam
pam { pam_auth = radiusd } pam 2facaut_pam { pam_auth = 2facaut_pam } pam horizon_pam { pam_auth = horizon_pam }
Which are three different instances of the PAM module.
- Here the debug log with separate horizon_pam configuration in the radius ... Tue Apr 18 12:08:41 2017 : Debug: Found Auth-Type = PAM Tue Apr 18 12:08:41 2017 : Debug: WARNING: Unknown value specified for Auth-Type. Cannot perform requested action.
If you have a "horizon_pam" module you need to put "horizon_pam" into the "authenticate" section. And, you need to set 'Auth-Type = horizon_pam" to use it.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html