Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So I have an openvpn running on a debian machine and I have set it up to work with PAM authentication via the pam module AND NOT the provided example script. However, requirements changed and now I need to start pushing specific client configuration to my users. After digging up a bit I used the client-config-dir directive and username-as-common-name but unfortunately my client specific settings aren't pushed. I suspect it is due to the fact that username-as-common-name might only be working if used with auth-user-pass-verify via-file setting. I'm pasting my configuration file here:

port 1194
proto udp
dev tun
keepalive 5 15
ca /etc/openvpn/keys/ca.crt
cert /etc/openvpn/keys/server.crt
key /etc/openvpn/keys/server.key
dh /etc/openvpn/keys/dh1024.pem
;push "redirect-gateway def1"
push "route"
push "route"
push "route"
push "route"
push "route"
push "route"
push "route"
push "route"
push "route"
push "route"
push "route"
push "route"
verb 5
log /var/www/random_log
status openvpn-status.log 7200
plugin /usr/lib/openvpn/ common-auth
;auth-user-pass-verify via-file
client-config-dir ccd

In essence I want client-specific settings to work AND to retain logging using the PAM module and not the provided script.

share|improve this question
client-config-dir works fine with username-as-common-name and plugin for me. Anything in the server logs? – mgorven Feb 11 '13 at 21:40

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.