By the way, this is using tomcat 8 and it's running on Linux. Windows
machines are the AD server and the client.
--
View this message in context:
http://tomcat.10.x6.nabble.com/Tomcat-windows-authentication-domain-login-issue-tp5023801p5023860.html
Sent from the Tomcat - User mailing list
Am 15.10.2014 um 03:48 schrieb tantaryu:
Okay, now I tried with a email client. Let's see if it works.
I need some idea on what's wrong with my tomcat configuration for windows authentication. I followed the tomcat windows authentication
tutorial and uses the manager web application comes with
Let's hope it works this time.
I need some idea on what's wrong with my tomcat configuration for windows
authentication. I followed the tomcat windows authentication tutorial and
uses the manager web application comes with tomcat to do a poc. In my
web.xml I change
Am 15.10.2014 um 10:22 schrieb tantaryu:
Let's hope it works this time.
If this was your try to add newlines, than I think it failed.
Felix
I need some idea on what's wrong with my tomcat configuration for windows authentication. I followed the tomcat windows authentication tutorial and uses
Okay, this might sounds funny. But how do I add a newlines?
Date: Wed, 15 Oct 2014 01:37:42 -0700
From: ml-node+s10n5023863...@n6.nabble.com
To: ming...@outlook.com
Subject: Re: Tomcat windows authentication domain login issue
Am 15.10.2014 um 10:22 schrieb tantaryu:
Let's hope it
maybe you are interested in this one:
https://github.com/Servoy/servoy-eclipse-tomcat
thats also a osgi enabled tomcat (but the full tomcat) we use that one
right in eclipse, where other plugins just contribute filters and servlets
On 14 October 2014 23:56, Achim Nierbeck
Hi Johan,
thanks for the pointer. To me it looks like it does have a different scope.
Pax Web has been one of the first OSGi HttpService providers with
additional support for Web Application Bundles (std. war with OSGi Manifest)
This has been achieved so far very successfully with Jetty. Now we
Am 15. Oktober 2014 11:05:59 MESZ, schrieb tantaryu ming...@outlook.com:
Okay, this might sounds funny. But how do I add a newlines?
I don't know how to do it in your mail client. But generally I would try to
configure it to not use html (only).
You could try another mal Client or provider.
yes we tried to go that way with whiteboard registration also (jetty is
shipped by default in eclipse also with that)
but that was way to hard to control and to really configure the way we want
so we decided to make tomcat a full osgi package itself.
On 15 October 2014 12:13, Achim Nierbeck
Hi Johan,
2014-10-15 12:22 GMT+02:00 Johan Compagner jcompag...@servoy.com:
yes we tried to go that way with whiteboard registration also (jetty is
shipped by default in eclipse also with that)
but that was way to hard to control and to really configure the way we want
so we decided to make
On 15/10/2014 11:38, Achim Nierbeck wrote:
Hi Johan,
2014-10-15 12:22 GMT+02:00 Johan Compagner jcompag...@servoy.com:
yes we tried to go that way with whiteboard registration also (jetty is
shipped by default in eclipse also with that)
but that was way to hard to control and to really
Hello:
I'm using Tomcat 6.0.24 and sometimes I'm getting an IOException like :
Caused by: java.io.IOException: No data available due to previous error
at
org.apache.coyote.http11.filters.ChunkedInputFilter.checkError(ChunkedInputFilter.java:588)
~[tomcat-coyote-6.0.24.jar:na]
at
Hi Mark,
thanks for the pointer I think I've found the reason.
Could it be that the initialization of the servlets changed from 7 to 8 :)
I used to load the servlet in the initialization phase. So that's the part
I need to alter.
Need to move that part to the loadOnStartup method call.
just in
Hi
Following the recent announcement of the SSLv3 POODLE vulnerability
(CVE-2014-3566), when disabling SSLv3 on Tomcat APR/Native using the
following configuration: SSLProtocol=TLSv1, it seems that the effect is
that besides the SSLv3 protocol even the TLSv1.1 and TLSv1.2 protocols no
longer
On 15/10/2014 13:42, John Blaut wrote:
Hi
Following the recent announcement of the SSLv3 POODLE vulnerability
(CVE-2014-3566), when disabling SSLv3 on Tomcat APR/Native using the
following configuration: SSLProtocol=TLSv1, it seems that the effect is
that besides the SSLv3 protocol even the
That isn't working for tomcat 6, it will only accept TLSv1 for the
SSLProtocol entry, and that results in in using TLS1.0 only.
On 10/15/2014 7:48 AM, Giles Coochey wrote:
On 15/10/2014 13:42, John Blaut wrote:
Hi
Following the recent announcement of the SSLv3 POODLE vulnerability
Thanks for your reply.
Kindly note that for SSL on Tomcat, I do not use the standard JSSE SSL but
OpenSSL via APR/native.
According to the documentation, the SSL protocols can be configured in this
manner for APR/native:
SSLProtocolProtocol which may be used for communicating with clients.
I am using Tomcat 7. I can reproduce the issue even on Native 1.1.30.
On Wed, Oct 15, 2014 at 3:00 PM, James Drews dr...@engr.wisc.edu wrote:
That isn't working for tomcat 6, it will only accept TLSv1 for the
SSLProtocol entry, and that results in in using TLS1.0 only.
On 10/15/2014 7:48
On 15/10/2014 14:03, John Blaut wrote:
I am using Tomcat 7. I can reproduce the issue even on Native 1.1.30.
Apologies, yes Apr/Native only supports SSLv2, SSLv3 TLSv1.0
|SSLProtocol|
Protocol which may be used for communicating with clients. The default
value is |all|, which is
When SSLv3 is enabled, it seems TLS1.1 and TLS 1.2 are supported however.
It seems strange that the SSLv3 option controls the availability of TLS1.1
and TLS1.2.
Now that SSLv3 is considered insecure and more people start to disable it,
I suppose many on APR/Native will encounter the same issue.
Thank you George Sexton for your explanations.
Best regards to you all.
--
View this message in context:
http://tomcat.10.x6.nabble.com/How-can-Tomcat-be-started-at-boot-time-as-a-non-root-user-tp5023810p5023899.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
John,
On Wednesday, October 15, 2014 6:20 AM, John Blaut john.bl...@gmail.com
wrote:
When SSLv3 is enabled, it seems TLS1.1 and TLS 1.2 are supported however.
It seems strange that the SSLv3 option controls the availability of TLS1.1
and TLS1.2.
Now that SSLv3 is considered insecure
Hi all
I was trying to enable ssl in my tomcat server. I dont know whether my
tomcat is using JSSE or APR. but as I created a keystore and imported a
cert into it , can I use JSSE type irrespective of the connector?
My server.xml block
Connector port=9443
On 16/10/2014 12:10 PM, Shashank shashank.rayap...@gmail.com wrote:
Hi all
I was trying to enable ssl in my tomcat server. I dont know whether my
tomcat is using JSSE or APR. but as I created a keystore and imported a
cert into it , can I use JSSE type irrespective of the connector?
My
24 matches
Mail list logo
