Re: Browser complains of "weak signature algorithm" in cert on a new Tomcat installation. Does anybody here know anything about that sort of thing

James, > Am 07.01.2021 um 00:34 schrieb James H. H. Lampert : > > We just had our first Tomcat 8.5 installation on a customer's AS/400. > > The customer apparently has his own CA (they're a big company), and when I > installed SSL in their Tomcat, and tested it with a browser, it complained,

Re: Browser complains of "weak signature algorithm" in cert on a new Tomcat installation. Does anybody here know anything about that sort of thing

On 1/6/21 3:46 PM, Robert Turner wrote: You'll want to set the protocols, ciphers, and honorCipherOrder ... The precise wording in the error message is: . . . but the server presented a certificate signed using a weak signature algorithm (such as SHA-1). . . . Which is to say, it doesn't

Re: Browser complains of "weak signature algorithm" in cert on a new Tomcat installation. Does anybody here know anything about that sort of thing

You'll want to set the protocols, ciphers, and honorCipherOrder attributes on either the Connector or the SSLHostConfig objects in your server.xml file to restrict the available TLS/SSL protocols and ciphers available to avoid using weak ones. See the documentation here for details:

Browser complains of "weak signature algorithm" in cert on a new Tomcat installation. Does anybody here know anything about that sort of thing

We just had our first Tomcat 8.5 installation on a customer's AS/400. The customer apparently has his own CA (they're a big company), and when I installed SSL in their Tomcat, and tested it with a browser, it complained, something to the general effect of "weak signature algorithm." While

Parallel deploy with /manager/text servlet

Hi, our system consists on about 80+ webapps on different servers. Multiple webapps are deployed per Tomcat server remotely using the manager and host-manager webapps. This has been working fine for years, however some servers now have 5+ webapps and they are taking a long time to start. We

Re: Request body is empty in Tomcat 9.0.38

If you can see the WSDL for the service assuming its a SOAP, then you can actually generate a sample client XML using SOAP GUI clients and verify if the service is actually deployed correctly On Wed, Jan 6, 2021, 7:59 AM Mounika Reddy wrote: > Check if it's a malformed XML and namespaces

Re: Request body is empty in Tomcat 9.0.38

Check if it's a malformed XML and namespaces qualified are right. If JSON it's a different issue and without much info, I hardly think it's a tomcat issue On Wed, Jan 6, 2021, 7:51 AM Jonnalagadda, Swathi (External) < swathi.jonnalaga...@xerox.com> wrote: > Hi > > We have a web application

Request body is empty in Tomcat 9.0.38

Hi We have a web application deployed in tomcat9.0.38 which is invoking a web service which is again deployed in another tomcat instance of 9.0.38 We are using httpclient to post request to webservice from the webapplication and we could see that the request is reaching the webservice

Re: Not able to make JSESSIONID cookie secure

Hi Amit, On Wed, Jan 6, 2021 at 11:15 AM Amit Khosla wrote: > Hi, > > Thanks for the reply. > > We tried the settings on multiple machines. And found that the same > configuration machines gave different results. > We are getting multiple jsessionid cookies being created. In our > application,

Re: Not able to make JSESSIONID cookie secure

Hi, Thanks for the reply. We tried the settings on multiple machines. And found that the same configuration machines gave different results. We are getting multiple jsessionid cookies being created. In our application, we have a multi tenant application. For each tenant we have an nginx running