2:44 p.m.
A custom Tomcat authenticator has been added to authenticate users
using client certificate if provided, otherwise it will fallback to
BASIC/FORM authentication.
The SSL connection has been configured with clientAuth="want" so
users can choose whether to provide a certificate or username and
password.
Ticket #107
Note: The cert-request-submit still needs to be moved out of
/pki/certrequests to allow access by unauthenticated users. Right now it
requires authentication and for some reason not working.
--
Endi S. Dewata
10:36 p.m.
On 7/26/2012 2:44 PM, Endi Sukma Dewata wrote:
A custom Tomcat authenticator has been added to authenticate users
using client certificate if provided, otherwise it will fallback to
BASIC/FORM authentication.
The SSL connection has been configured with clientAuth="want" so
users can choose whether to provide a certificate or username and
password.
Ticket #107
Note: The cert-request-submit still needs to be moved out of
/pki/certrequests to allow access by unauthenticated users. Right now it
requires authentication and for some reason not working.
After restarting the server it seems to be working properly.
--
Endi S. Dewata
8:18 a.m.
On 7/26/2012 2:44 PM, Endi Sukma Dewata wrote:
A custom Tomcat authenticator has been added to authenticate users
using client certificate if provided, otherwise it will fallback to
BASIC/FORM authentication.
The SSL connection has been configured with clientAuth="want" so
users can choose whether to provide a certificate or username and
password.
Ticket #107
Note: The cert-request-submit still needs to be moved out of
/pki/certrequests to allow access by unauthenticated users. Right now it
requires authentication and for some reason not working.
New patch attached. This patch contains the authenticator only. The SSL
configuration will be modified in a later patch.
Please apply in this order: 85-1, 87, 88, 86-1.
--
Endi S. Dewata
4286
days inactive
4292
days old
3 comments
1 participants
participants (1)
-
Endi Sukma Dewata