On 13.03.2020 17:53, Stephane Passignat wrote:
Hi,
Actually I have Apache2 operating as proxy and authenticate layer (HTTP
Form and HTTP Basic), in front of several Tomcat instances and webapps.
Apache pushes the userId to tomcat through AJP.
On tomcat side, the webapp has a Basic login-module i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Luis,
On 3/13/20 14:28, Luis Rodríguez Fernández wrote:
> Hello Stephane,
>
>> moving authentication at tomcat level with an openid Realm
>
> If I understand you correctly you want to make the authentication
> process in tomcat instead of delegating
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Siva,
On 3/12/20 23:13, siva.saravanamu...@csl.com.au wrote:
> Below is the catalina.log output
>
> 12-Mar-2020 19:57:18.885 INFO [main]
> org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler
> ["https-openssl-apr-8443"] 12-Mar-2020 19:5
Hello Stephane,
> moving authentication at tomcat level with an openid Realm
If I understand you correctly you want to make the authentication process
in tomcat instead of delegating in your apache proxy, don't you ? I would
have a look then at the tomcat keycloak adapter [1]. Me I am using the S
Hi,
Actually I have Apache2 operating as proxy and authenticate layer (HTTP
Form and HTTP Basic), in front of several Tomcat instances and webapps.
Apache pushes the userId to tomcat through AJP.
On tomcat side, the webapp has a Basic login-module in web.xml.
I'm quite satisfied of the result, au
On Fri, Mar 13, 2020 at 10:09 AM Mark Thomas wrote:
>
> On 13/03/2020 13:54, Chris Cheshire wrote:
> > Using 9.0.31 on Java 8, I have my AJP connector configured as
> >
> > > secretRequired="false" />
> >
> > According to the logs, this is defaulting to the NIO protocol.
>
> Correct.
>
> > The
>
On 13/03/2020 13:54, Chris Cheshire wrote:
> Using 9.0.31 on Java 8, I have my AJP connector configured as
>
> secretRequired="false" />
>
> According to the logs, this is defaulting to the NIO protocol.
Correct.
> The
> connector comparison chart [1] implies that NIO2 is used for 8.5x
> onwar
On 13/03/2020 13:52, Heinrich Michael (PS-EC/EBT3) wrote:
> Hello all,
>
> I found out that I've trouble in uploading multipart messages with TLS in
> Tomcat 9.0.31 (Windows server 2012/2016, Java 1.8.0_241, also 221). With the
> same server config in 9.0.30 it works well. Uploading multipart me
Using 9.0.31 on Java 8, I have my AJP connector configured as
According to the logs, this is defaulting to the NIO protocol. The
connector comparison chart [1] implies that NIO2 is used for 8.5x
onwards.
Shouldn't the AJP/1.3 protocol alias be using NIO2 by default (I don't
have APR/native insta
Hello all,
I found out that I've trouble in uploading multipart messages with TLS in
Tomcat 9.0.31 (Windows server 2012/2016, Java 1.8.0_241, also 221). With the
same server config in 9.0.30 it works well. Uploading multipart messages in
9.0.31 without TLS works also. This can be reproduced whe
Mark,
Thanks. You waken my frozen concentration. Yes I was able to identify the error
which is related APR library and I followed the step as per this article
https://www.openkm.com/wiki/index.php/Tomcat_native_libraries
which made port 8443 listen and able to load the URL with the certificate.
Hello tomcat user group,
Today I solved my problem with the empty manager responses.The issue does not
occur any more when using the new Java11-HTTP-Client to call the
tomcat-manager.My old implmentation of the client was based on very old java
functionality.
So I do not know whether it was an
>>Are you able to make other /manager requests and get a good response?
YES,all other manager requests work and also the stop command works in some
cases.
We have a destroy method in our Servlet implemented that needs some seconds
when the app is stopped. This destroy method can take more time t
Thanks Christopher,
Am 12.03.2020 um 16:11 schrieb Christopher Schultz:
> The complete new default pattern is:
>
>
> (javax\.servlet\.request\.(cipher_suite|key_size|ssl_session|X509Certifi
> cate)|CERT_(ISSUER|SUBJECT|COOKIE|FLAGS|SERIALNUMBER)|HTTPS_(SERVER_SUBJ
> ECT|SECRETKEYSIZE|SERVER_ISSUER
Please provide the complete catalina.log for a clean failed start.
To be specific:
- make sure Tomcat is not running
- delete all the files in the logs directory
- start Tomcat
- wait for start-up to complete
- provide us with the full catalina.log
Mark
On 13/03/2020 03:13, siva.saravanamu...@
15 matches
Mail list logo