Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. 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

I was asked to do it "Configure SSL Mutual (Two-way) Authentication" and I don't know where to start or how to test it .
server and many clients . they can access code on server only if they have a signed certificate from server . and server can generate those certificates and disable them here a tutorial but I'm so scared of losing connection with server I'm working on because it's the main server if I re-generate new keys .
do I have to be a root user ?
is there's any bash for this ?
any information would be appreciated .

share|improve this question
If you're tasked with setting up security for infrastructure like this, you should start elsewhere. Setting up a secure implementation of client certificate verification when it really matters is not something you should really be doing without prior experience in setting up secure systems. – Chris Down Apr 25 '13 at 10:10
experience comes when you try to do something . I'm reading about it . just needed guide lines from u guys to not got lost while browsing and searching :) – SafeY Apr 25 '13 at 10:34
Here is a good tutorial to get you started: codeproject.com/Articles/326574/… and a 15 minute guide, monduke.com/2006/06/04/…;. In general the setup of 2 way SSL is going to be highly dependent on the technologies you're trying to implement it on, Java, Apache, etc. We'd need that info as well to help narrow the scope. Do you know any of this? – slm Apr 25 '13 at 11:15
yes , of course :D , is it for apache on a centos server – SafeY Apr 25 '13 at 11:25

Standard/Usual HTTPS enables you to establish the identity of the server from a common trusted root CA, importing a client's SSL certificate in the browser (that is marked as enabled for authentication) is how you use SSL certs to perform client authentication. The end result is the client browser authenticates the server via HTTPS and the server authenticates the client via the client's authentication certs.

This tutorial describes the process of configuring apache for client ssl authentication/verification, which is the only non-usual part of the process. It's just a set of 3 or 4 directives to add to the virtual host configuration.

share|improve this answer
Thanks , What's the web server !? I have a server which holds apache and client wants to reach a page on this server . This server will be responsible on generating certificates for clients and signing them . what the third party for ? what am i missing ? – SafeY Apr 25 '13 at 13:13
That tutorial used self-sign certificates to provide you with example. You can skip the "openssl" commands if you're getting your certs from an actual certificate authority. – Bratchley Apr 25 '13 at 14:27

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.