RE: Tomcat 9: Client Certificate verification setting with optional is not working

other details required by Tomcat 9 for this use case? Regards Manish -Original Message- From: Palod, Manish Sent: Wednesday, May 5, 2021 9:21 AM To: Tomcat Users List Subject: RE: Tomcat 9: Client Certificate verification setting with optional is not working Hi Mark, Thank you for

RE: Tomcat 9: Client Certificate verification setting with optional is not working

rs@tomcat.apache.org Subject: Re: Tomcat 9: Client Certificate verification setting with optional is not working CAUTION: External email. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 04/05/2021 18:17, Palod, Manish wrote: > Hi, &g

Tomcat 9: Client Certificate verification setting with optional is not working

Hi, We are in process of migrating from Tomcat 7 to Tomcat 9. We use cert-based client authentication in our application, support password-based and cert-based authentication. For this purpose, we are setting certificateVerification="optional" attribute in SSLHostConfig Element of Server.xml [

RE: Tomcat 9: Application in not starting with TrustStore attributes

attributes CAUTION: External email. Do not click links or open attachments unless you recognize the sender and know the content is safe. Manish, > -Original Message- > From: Palod, Manish > Sent: Tuesday, April 20, 2021 8:37 AM > To: users@tomcat.apache.org > Subject: Tomcat

Tomcat 9: Application in not starting with TrustStore attributes

Hi, We are in process of upgrading Tomcat 7 to Tomcat 9 and stuck with Trust store settings for Client certificate, following is the connector setting: Application is working properly when truststoreFile, truststorePassword and truststoreType attrib

RE: Tomcat 7: logs for failure request with unsupported cipher and unsupported SSL protocol

, February 3, 2020 7:32 PM To: users@tomcat.apache.org Subject: Re: Tomcat 7: logs for failure request with unsupported cipher and unsupported SSL protocol -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Manish, On 2/2/20 11:20 PM, Palod, Manish wrote: > Thanks Chris for considering this for fut

RE: Tomcat 7: logs for failure request with unsupported cipher and unsupported SSL protocol

with unsupported cipher and unsupported SSL protocol -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Manish, On 1/31/20 8:01 PM, Palod, Manish wrote: > I will look forward for future release with enhanced info about > connection. https://bz.apache.org/bugzilla/show_bug.cgi?id=64110 Patch

RE: Tomcat 7: logs for failure request with unsupported cipher and unsupported SSL protocol

with unsupported cipher and unsupported SSL protocol -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Manish, On 1/30/20 3:12 AM, Palod, Manish wrote: > Thanks Mark and Chris for providing the info. > >> IIRC, we are parsing a little of the initial handshake packet for a >> fe

RE: Tomcat 7: logs for failure request with unsupported cipher and unsupported SSL protocol

/29/20 7:56 AM, Mark Thomas wrote: > On 29/01/2020 12:40, Palod, Manish wrote: >> Hi All, >> >> >> I am using tomcat 7 and in our server we support connection only with >> "TLSv1.2" and cipher "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256". >

Tomcat 7: logs for failure request with unsupported cipher and unsupported SSL protocol

Hi All, I am using tomcat 7 and in our server we support connection only with "TLSv1.2" and cipher "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256". Following is the Access valve pattern "%{E M/d/y @ hh:mm:ss.S a z}t %a (%{X-Forwarded-For}i) > %A:%p "%r" %{requestBodyLength}r %D %s %B %I "%{Referer}i"

RE: Antwort: Tomcat 7: Access Valve pattern cipher, SSL Protocol

> > i think you can do it with: > > JAVA_OPTS="$JAVA_OPTS -Djavax.net.debug=ssl,handshake" That won't do what the OP asked. These should work: %{javax.servlet.request.cipher_suite}r %{org.apache.tomcat.util.net.secure_protocol_version}r Mark > > Regard

Tomcat 7: Access Valve pattern cipher, SSL Protocol

Hi All, I am using tomcat 7 and for audit purpose, want to see cipher and SSL protocol used in the request. How should I mention these attributes in the Access Valve pattern to get these info in the logs. Regards Manish

application is not working after migrating from tomcat 7.0.70 to tomcat 8.5.5

Hi All, I am in process of migrating my application from tomcat 7.0.70 to 8.5.5 and getting some issues My connector settings of 7.0.70 is And connector settings of 8.5.5 is

tomcat 7.0.70 redirection is not working as expected with https

Hi All, Previously I was using apache web server and tomcat for SSL redirection and web server, in that case redirection from apache to tomcat was working fine. Now I have removed the apache web server and using tomcat only for ssl settings also [server.xml sslEnabled and other related settings]

RE: response.sendRedirect is not working in application after upgrade from 7.0.65 to 7.0.67

7.0.65 to 7.0.67 Hi, 2016-03-24 8:18 GMT+02:00 Palod, Manish : > > Hello Experts, > We are using tomcat in our application from many years and things were working fine. > > After upgrade from tomcat 7.0.65 to 7.0.67, response.sendRedirect is > not working properly in appli

response.sendRedirect is not working in application after upgrade from 7.0.65 to 7.0.67

Hello Experts, We are using tomcat in our application from many years and things were working fine. After upgrade from tomcat 7.0.65 to 7.0.67, response.sendRedirect is not working properly in application. We are having spaces in between url attributes all the time ex. companyName=XYZ Inc&Addr