Hello, I was working with free radius 3.0.12 and received the below errors in debug output. lm_sql (sql): Released connection (0) (0) [sql] = ok (0) [expiration] = noop (0) [logintime] = noop (0) pap: WARNING: No "known good" password found for the user. Not setting Auth-Type (0) pap: WARNING: Authentication will fail unless a "known good" password is available (0) [pap] = noop (0) } # authorize = ok (0) ERROR: No Auth-Type found: rejecting the user via Post-Auth-Type = Reject (0) Failed to authenticate the user (0) Using Post-Auth-Type Reject I was reading this : Qoute < When a RADIUS packet contains a clear-text password in the form of a User-Password attribute, the/rlm_pap/module may be used for authentication. The module requires a "known good" password, which it uses to validate the password given in the RADIUS packet. That "known good" password must be supplied by another module (e.g./rlm_files/,/rlm_ldap/, etc.), and is usually taken from a database. Unqoute > But I'm having a bit of trouble understanding. In my DB the Attribute is Cleartext-Password , which corresponds to a plain text password. So then why is this error generated. And how to mitigate it. What am I missing. The authorize section of my /etc/raddb/sites-enabled/default is read as: authorize { preprocess digest suffix sql expiration logintime pap } and authenticate as : authenticate { } Auth-Type PAP { pap } digest } Please let me know if any further information is required. Any help is greatly appreciated. -- *Mustafa Mujahid | Systems* /Operations Engineer/