Develop Reference

Tomcat versione 8.5.69 and sameSiteCookies=lax doesnt work with saml/onelogin

I have a web application that run on tomcat 8.5.34 and use the single sign on login with saml/onelogin api.
Here the specifications:
Amazon corretto Jdk 1.8.0_252
Apache tomcat 8.5.34
OS Windows 10
java-saml-2.4.0.jar and java-saml-core-2.4.0.jar
Everithing was fine until we upgrade the tomcat version to 8.5.69, from that version the redirect to our application stopped to work.
Here every attempt to fix the issue:
Upgrade the java-saml api --> fail
Upgrade the tomcat version till the last 9 release --> fail
Change the attribute classname in the tag CookieProcessor to the org.apache.tomcat.util.http.LegacyCookieProcessor --> fail
After all we found two solutions:
Downgrade the tomcat version (that is not possible in production server, we are migrating to tomcat 9)
Change the attribute sameSiteCookies in this configuration in context.xml <CookieProcessor sameSiteCookies="lax"/> from lax to unset, but this configuration involve my application in a security problem named CSRF attacks so i cant pass VAPT tests.
Now i am in a bottleneck, any suggestions?
Thanks to the all community.

Activiti Explorer - Request resource is not available

I have big problem to run activiti-explorer when i try access: http://localhost:8080/activiti-explorer/ tomcat shows me HTTP Status 404 - The requested resource is not available. I'm really don't have any idea why that dosen't work. Can you help me?
This what have I done on my PC:
I'm using 5.19.0 version of activiti-explorer
7.0.63 tomcat
JDK 1.8.0.77 (i think there is no point to downgrade java to previous versions (<=1.7) becouse my main application using this version)
I'm sure I have correctly configured environment variables (JAVA_HOME,JRE_HOME,PATH,CATALINA_HOME)
I configured data base connection (db.properties, context.xml) in activiti-explorer.war and i moved this file to tomcat/webapps
I don't have any errors about activiti during tomcat start

Check if activiti explorer is deployed to tomcat in manager.
http://{host}:{port}/manager/html
More info in https://tomcat.apache.org/tomcat-7.0-doc/manager-howto.html

Check the catalina.out log. There will be something in there that leads you to the solution.

Check Admin Console (cmd that runs behind) after hitting the link. most recent exception occurred will be displayed there.

Run JHipster in production profile - no database connection

I have a problem with running JHipster in Production Mode. After building the .war by
mvn -Pprod package
and uploading it to my server, I get the "normal" start page - so the page loaded, but with following errors:
"NetworkError: 404 Not Found - http://server.net:9080/studentenhelfer-intern-0.0.1-SNAPSHOT.original/api/authentication?cacheBuster=1459611519471"
"NetworkError: 404 Not Found - http://server.net:9080/studentenhelfer-intern-0.0.1-SNAPSHOT.original/api/logout?cacheBuster=1459611519626"
The second point - when I "install/start" the Application on the server, the database will be not created. (No tables and no data)
I can´t figure out why.... With the dev-profile everything is working fine.... (Also with the same DB settings in application-prod.yml)
Additionial Info: the spring profile has also been set to prod profile in
/etc/default/tomcat7
JAVA_OPTS="${JAVA_OPTS} -Dspring.profiles.active=prod"
(This should be ok, yes?)
I´m using MySql as Db (with liquibase) and Maven for building. The server is a linux server (ubuntu) with Plesk 12.
For information - that´s my first experience with a linux-server. So maybe I forgot some extra configurations, but I think if the page gets loaded, the tomcat should not be the problem)
I also can´t find any "usefull" logs from catalina or tomcat...
var/log/tomcat7/catalina.out
var/log/apache2/error.log
But if someone needs to see the logs, I will post them..
Please help :(
Thanks, Fab
EDIT: I have tried to run the application on a local running tomcat -> And it works... so it´s a server-side problem?

My Pivotal tc Server not Start

Until a few days ago, my STS worked perfectly, but of a sudden, the Pivotal server does not start, throws me the following error message when you run an application:
SEVERE: Class loader creation threw exception
java.io.IOException: The filename, directory name, or volume label syntax is incorrect
at java.io.WinNTFileSystem.canonicalize0 (Native Method)
at java.io.Win32FileSystem.canonicalize (Win32FileSystem.java: 414)
at java.io.File.getCanonicalPath (File.java: 618)
at java.io.File.getCanonicalFile (File.java: 643)
at org.apache.catalina.startup.ClassLoaderFactory.createClassLoader (ClassLoaderFactory.java: 170)
at org.apache.catalina.startup.Bootstrap.createClassLoader (Bootstrap.java: 149)
at org.apache.catalina.startup.Bootstrap.initClassLoaders (Bootstrap.java: 90)
at org.apache.catalina.startup.Bootstrap.init (Bootstrap.java: 226)
at org.apache.catalina.startup.Bootstrap.main (Bootstrap.java: 425)
They could help me with this problem?
From already, thank you very much for your attention and time.
Gustavo Echenique

I had the same error on Tomcat 6 (Pivotal 3.0, STS) and my problem was in catalina.properties. The "common.loader" property was incorrectly using Tomcat 8 style and it was as follows:
common.loader = \
\"${catalina.base}/lib\",\
\"${catalina.base}/lib/*.jar\",\
\"${catalina.home}/lib\",\
\"${catalina.home}/lib/*.jar\"
I have removed the double quotes and that fixed the problem. Correct definition:
common.loader = \
${catalina.base}/lib,\
${catalina.base}/lib/*.jar,\
${catalina.home}/lib,\
${catalina.home}/lib/*.jar
Also, STS has quietly added Tomcat 8 JARs (bootstrap.jar, etc) to my Tomcat 6 launch configuration. While I had these JARs on the classpath, everything worked fine. But once I discovered and removed them, Tomcat 6 started breaking with the error in the original post.

I started to have the same issue out of nothing as well. We are using Java 1.7 in our project, but I also have Java 8 installed on my machine for experimenting. Even though everything is still configured to use 1.7 (I never changed the configuration and it was working fine), I think after some Java 8 update I started to get this issue.
After trying several things, I decided to uninstall all Java 8 related updates and installations; and made a fresh installation of Spring STS 3.6.2 with a new workspace. It seems to be working fine right now. You can try this if you also have a similar environment.

BeanLocator has not been set (Installing Liferay on Tomcat 7.0)

I'm looking to install the Liferay portal on Tomcat without using the bundle.
Here a link to the tutorial I'm following:
https://www.liferay.com/documentation/liferay-portal/6.1/user-guide/-/ai/lp-6-1-ugen11-installing-liferay-on-tomcat-7-0
Tomcat is running at localhost:8080 as expected, but the Liferay portal is throwing an error. I've followed these directions twice now and can't find a way around it:
HTTP Status 500 - com.liferay.portal.kernel.bean.BeanLocatorException: BeanLocator has not been set
When I navigate to index.jsp (in the webapps/root folder) the line at fault is line #57.
56 else {
57 redirect = PortalUtil.getHomeURL(request);
58 }
According to the Liferay forums, I'm not the first to run into this error, but I wasn't able to find a solution. Thoughts?
Additional Notes:
Operating System: Windows 7
Liferay Portal Source: liferay-portal-src-6.2-ce-ga2
Liferay Portal War: liferay-portal-6.2.0-ce-ga1-20131101192857659.war
Apache Tomcat Version 7.0.53: apache-tomcat-7.0.53