Discussion:
[courier-users] Authenticate Clients via TLS client cert
Bernd Wurst
2017-07-02 20:09:58 UTC
Permalink
Hello,

I'm struggling with the question if it is possible to authenticate
clients (optionally) with a client certificate. I found some docs about
dovecot implementing this [1] and was wondering if courier (SMTP) could
also be used with this?

I could not find something about it in the docs.


The desired use would be that we operate a local CA and issue
certificates that contain a user name (e-mail-address) as common name
and courier authenticates this certificate as the given user, so that
logging and processing will continue have the sender's data.

[1]: "Client certificate verification/authentication", half way down at
https://wiki.dovecot.org/SSL/DovecotConfiguration


regards,
Bernd
Sam Varshavchik
2017-07-02 21:06:45 UTC
Permalink
Post by Bernd Wurst
Hello,
I'm struggling with the question if it is possible to authenticate
clients (optionally) with a client certificate. I found some docs about
dovecot implementing this [1] and was wondering if courier (SMTP) could
also be used with this?
I could not find something about it in the docs.
The desired use would be that we operate a local CA and issue
certificates that contain a user name (e-mail-address) as common name
and courier authenticates this certificate as the given user, so that
logging and processing will continue have the sender's data.
[1]: "Client certificate verification/authentication", half way down at
https://wiki.dovecot.org/SSL/DovecotConfiguration
http://www.courier-mta.org/install.html#sslcert

Also described further in the esmtpd-ssl configuration file, under
TLS_EXTERNAL.

For this to work, the certificate subject needs to specify whatever would be
used for the login ID when authenticating manually.
Bernd Wurst
2017-07-03 19:37:32 UTC
Permalink
Hello.

[sorry for sending this via private mail before. my fault.]
Post by Sam Varshavchik
http://www.courier-mta.org/install.html#sslcert
Also described further in the esmtpd-ssl configuration file, under
TLS_EXTERNAL.
For this to work, the certificate subject needs to specify whatever
would be used for the login ID when authenticating manually.
Wow, perfect. I missed that completely.

Tank you for the pointer!

regards,
Bernd

Loading...