-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andrew,
On 12/1/14 4:32 PM, Andrew Gronosky wrote:
> Problem solved.
>
> The issue was tomcat-users.xml should contain the client's CN as
> the user name, like this:
>
>username="CN=client1, OU=Application Development, O=GoSmarter,
> L=Bangal
Problem solved.
The issue was tomcat-users.xml should contain the client's CN as the
user name, like this:
So Chris was definitely on the right track when he (I assume, maybe
incorrectly, "Chris" is male) inquired about the CNs in my client certs.
Thanks again, Chris!
-Andrew Gronosk
On 2014-12-01 15:14, Christopher Schultz wrote:
What do the CNs look like for your client certs?
- -chris
Hi Chris,
Thanks for the very quick reply!
For the testClient_2 client cert, the CN is:
Owner: CN=testClient_2, OU=ATAK, O=BBN, L=Cambridge, ST=MA, C=US
Issuer: CN=marti-ca, O=BBN, L=C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andrew,
On 12/1/14 2:33 PM, Andrew Gronosky wrote:
> Hello,
>
> I am trying to set up client-certificate authentication for Tomcat
> 7.0.57. I have read the basics in the docs and I have my
> configuration working up to a point.
>
> My problem is
Hello,
I am trying to set up client-certificate authentication for Tomcat
7.0.57. I have read the basics in the docs and I have my configuration
working up to a point.
My problem is that Tomcat accepts the client's connection, but returns
HTTP status 401 for pages the user is supposed to be
