On 14 Mar 2015, at 3:43 PM, Graham Leggett minf...@sharp.fm wrote:
Changing the auth-type to CLIENT-CERT shows that the username has been
replaced by the subject-DN of the cert, which is progress.
Reverse engineering tomcat showed that the tomcatAuthentication parameter
solved half the
On 14 Mar 2015, at 1:04 AM, Konstantin Kolinko knst.koli...@gmail.com wrote:
You are using JRE's default java.util.logging.LogManager.
You need to configure JRE to use the Tomcat JULI implementation of log
manager with
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
The
Graham,
On Fri, Mar 13, 2015 at 3:02 PM, Graham Leggett minf...@sharp.fm wrote:
Hi all,
I have a working realm installation using basic authentication, which I
need to switch to client certificate authentication. Having done so it
doesn’t work, I just get “forbidden”, with no indication of
On 13 Mar 2015, at 9:58 PM, Neven Cvetkovic neven.cvetko...@gmail.com wrote:
Just to confirm, the 403 Forbidden page was rendered by Tomcat, not Apache
HTTPD?
Yes, it is branded tomcat and appears in the tomcat access log.
I don't expect it is an Apache issue here - because you mentioned
Graham,
On Fri, Mar 13, 2015 at 4:43 PM, Graham Leggett minf...@sharp.fm wrote:
On 13 Mar 2015, at 9:58 PM, Neven Cvetkovic neven.cvetko...@gmail.com
wrote:
Just to confirm, the 403 Forbidden page was rendered by Tomcat, not
Apache
HTTPD?
Yes, it is branded tomcat and appears in the
2015-03-13 23:43 GMT+03:00 Graham Leggett minf...@sharp.fm:
On 13 Mar 2015, at 9:58 PM, Neven Cvetkovic neven.cvetko...@gmail.com wrote:
Just to confirm, the 403 Forbidden page was rendered by Tomcat, not Apache
HTTPD?
Yes, it is branded tomcat and appears in the tomcat access log.
I don't
2015-03-13 22:02 GMT+03:00 Graham Leggett minf...@sharp.fm:
Hi all,
I have a working realm installation using basic authentication, which I need
to switch to client certificate authentication. Having done so it doesn’t
work, I just get “forbidden”, with no indication of the error involved.
