Assessing and Updating MicroStrategy Customizations for Spring 6 Compatibility

Director, Application Security Engineering • MicroStrategy

Certain customizations need to be updated to be compatible with Spring 6. This article details assessing and provides some guidance on making updates.

Strategy is upgrading to Spring 6 along with Tomcat 10.1.x and JBoss 8 with the June 2024 release. For further details about this change, please see: 2024 Platform Certification Changes (microstrategy.com). Previous versions of Strategy used Spring 5 with Tomcat 9.x or JBoss 7. Certain customizations will need to be updated in order to continue working with Spring 6.
Tomcat 10.1.x and JBoss 8 implement the Servlet 6.0, JSP 3.1, EL 5.0, WebSocket 2.1 and Authentication 3.0 specifications (the versions required by Jakarta EE 10 platform). There is a significant breaking change between previous versions. The Java package used by the specification APIs has changed from javax.* to jakarta.*.
Internally Strategy will upgrade all the shipped components to conform to the new specifications. There is chance that some customizations built on top of Strategy platform might be impacted. The following details aim to ensure a smooth transition.

Assessment

The first step is to evaluate if the customizations or plugins are impacted by this upgrade. This depends mostly on if the java code in the customization is depending on a library that uses older version of the specifications. Please refer to the table in the next section to find a list of dependencies that requires upgrade. It is also recommended to test the plugins with the latest Strategy version on Tomcat 10.1.x to identify functionality issues that might be introduced.
The majority of Strategy plugins are likely to not be affected. These most often include:

Mapping License Keys
Custom Map
CSS Interface Customizations
Plugins for .XML File Settings Changes
Font Plugins

The reason these are likely not impacted is that they often only use JavaScript, HTML, Images, Font, Text or XML Config files.
Impacted plugins would likely use Java or Spring code, including:

Custom authentication plugins which use Spring
Custom ESMs for Strategy Web
Custom Java Beans for Strategy Web

Upgrading Process

Once the assessment concludes that the customizations will need to be upgraded, please follow these steps.

Upgrade 3rd Party Dependencies

Update your dependencies:

For Maven users, update the pom.xml file
For Gradle users, update the build.gradle file

During the upgrade, ensure to thoroughly review the migration documentation and release notes, paying special attention to any deprecated APIs that have been removed. Make necessary adjustments as required.
Here is a list of 3rd libs used in Strategy platform that need to be changed in order to support of Tomcat 10. The library name is provided in group.id:artifact-id notation. Please be aware that there might be libraries that are not listed here but still require upgrade in your own customizations.

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

ComponentStrategy ReleaseStrategy One: Cloud Hosted: Action Needed?Strategy On-Premise using bundled Tomcat: Action Needed?Strategy On-Premise not using bundled Tomcat: Action Needed?March 2024NoNoYes, updated configuration to use Java 17June 2024NoNoYes, upgrade web application server to Tomcat 10.1 or JBoss 8June 2024Yes, if you have Spring based customizations, commonly for authentication or Strategy Web.Yes, if you have Spring based customizations, commonly for authentication or Strategy Web.Yes, if you have Spring based customizations, commonly for authentication or Strategy Web.ComponentVersionActionTiming8.5.xRemovedMarch 20249.0.xRemovedJune 202410.1.xAddedJune 20247.2+ EAPRemovedJune 20248 EAPAddedJune 2024Library NameUpgraded to Which OneRepositoryjavax.servlet:servlet-apijakarta.servlet:jakarta.servlet-api with the latest stable release
i.e version 6.0.0https://mvnrepository.com/artifact/jakarta.servlet/jakarta.servlet-apijavax.servlet.jsp:jsp-apijakarta.servlet.jsp:jakarta.servlet.jsp-api with the latest stable release
i.e. version 3.1.1https://mvnrepository.com/artifact/jakarta.servlet.jsp/jakarta.servlet.jsp-apijavax.annotation:javax.annotation-apijakarta.annotation:jakarta.annotation-api with the latest stable release
i.e. version 2.1.1https://mvnrepository.com/artifact/jakarta.annotation/jakarta.annotation-apijavax.json:javax.json-apijakarta.json:jakarta.json-api with the latest stable release
i.e. version 2.1.3https://mvnrepository.com/artifact/jakarta.json/jakarta.json-apiorg.glassfish:javax.jsonorg.glassfish:jakarta.json with the latest stable release
i.e. version 2.0.1https://mvnrepository.com/artifact/org.glassfish/jakarta.jsonjavax.activation:activationjakarta.activation:jakarta.activation-api with the latest stable release
i.e. version 2.1.3https://mvnrepository.com/artifact/jakarta.activation/jakarta.activation-apijavax.validation:validation-apijakarta.validation:jakarta.validation-api with the latest stable release
i.e. version 3.0.2https://mvnrepository.com/artifact/jakarta.validation/jakarta.validation-apiio.swagger.core.v3:swagger-jaxrs2io.swagger.core.v3:swagger-jaxrs2-jakarta with the latest stable release
i.e. version 2.2.21https://mvnrepository.com/artifact/io.swagger.core.v3/swagger-jaxrs2-jakartajavax.xml.bind:jaxb-apijakarta.xml.bind:jakarta.xml.bind-api with the latest stable release
i.e. 4.0.2https://mvnrepository.com/artifact/jakarta.xml.bind/jakarta.xml.bind-apiSpring Framework and Spring BootUpgrade to Spring Framework 6.x and Spring Boot 3.x

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

sudo pip3 install --upgrade urllib3==1.19.1

sudo pip3 install --upgrade requests

rm -rf /opt/monitoring

mkdir /opt/monitoring

cd /opt/monitoring

aws configure set default.s3.signature_version s3v4

aws s3 cp s3://securecloud-config-prod-{region}/codedeploy/monitoring.zip . --region {region} //i.e.aws s3 cp s3://securecloud-config-prod-ap-northeast-1/codedeploy/monitoring.zip . --region ap-northeast-1

unzip monitoring.zip

sh scripts/add_cron_job.sh

https://mvnrepository.com/artifact/org.springframework https://mvnrepository.com/artifact/org.springframework.boot/spring-bootSpring SecurityUpgrade to Spring Security 6.x, including SAML and OAuth2 provider; please follow the migration guide:

Also upgrade Spring Security Kerberos to 2.x.https://mvnrepository.com/artifact/org.springframework.security https://mvnrepository.com/artifact/org.springframework.security/spring-security-saml2-service-provider https://mvnrepository.com/artifact/org.springframework.security/spring-security-oauth2-jose https://mvnrepository.com/artifact/org.springframework.security/spring-security-oauth2-client https://mvnrepository.com/artifact/org.springframework.security.kerberos/spring-security-kerberos-core https://mvnrepository.com/artifact/org.springframework.security.kerberos/spring-security-kerberos-web https://mvnrepository.com/artifact/org.springframework.security.kerberos/spring-security-kerberos-clientorg.glassfish.jersey.ext:jersey-spring5org.glassfish.jersey.ext:jersey-spring6 with the latest stable release
i.e. version 3.1.5https://mvnrepository.com/artifact/org.glassfish.jersey.ext/jersey-spring6io.jsonwebtoken:jjwtJJWT is separated into a few modules:

Need to upgrade to the above three modules with the latest stable release i.e. version 0.12.5, refer to jwtk/jjwt: Java JWT: JSON Web Token for Java and Android (github.com)https://mvnrepository.com/artifact/io.jsonwebtoken/jjwt-api https://mvnrepository.com/artifact/io.jsonwebtoken/jjwt-impl https://mvnrepository.com/artifact/io.jsonwebtoken/jjwt-jackson or https://mvnrepository.com/artifact/io.jsonwebtoken/jjwt-gsonApache TaglibsApache Taglibs does not support Servlet 6.0. Please consider changing to use JSTL implementation from Eclipse EE4J.https://mvnrepository.com/artifact/jakarta.servlet.jsp.jstl/jakarta.servlet.jsp.jstl-api https://mvnrepository.com/artifact/org.glassfish.web/jakarta.servlet.jsp.jstlcom.fasterxml.jackson.datatype:jackson-datatype-jsr353com.fasterxml.jackson.datatype:jackson-datatype-jakarta-jsonpwith the latest stable release
i.e. version 2.17.0https://mvnrepository.com/artifact/com.fasterxml.jackson.datatype/jackson-datatype-jakarta-jsonpBean nameChangesmstrSamlAuthnRequestFilterSAML bean with base class replaced:

old: org.springframework.security.saml2.provider.service.servlet.filter.Saml2WebSsoAuthenticationRequestFilter

new: org.springframework.security.saml2.provider.service.web.Saml2WebSsoAuthenticationRequestFiltersamlAuthenticationRequestContextResolverSAML bean with base class replaced; the customization are now performed in the property beans instead of the resolver itself; therefore, we no long extend the resolver to add customization codes

old: com.Strategy.auth.saml.authnrequest.SAMLAuthenticationRequestContextResolver

new: org.springframework.security.saml2.provider.service.web.authentication.OpenSaml4AuthenticationRequestResolver

The new resolver now accept 2 bean properties for customization:

authnRequestCustomizer: perform extra customization on generated AuthnRequest

relayStateResolver: populate “relay state” for the SAML SSO request

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

SAML beans removed because samlAuthenticationRequestContextResolver is updated to use new class; please consider extending com.Strategy.auth.saml.authnrequest.SAMLAuthenticationAuthnRequestCustomizer to customize AuthnRequestrelyingPartyRegistrationResolvercom.Strategy.auth.saml.config.SAMLRelyingPartyRegistrationResolver no longer deduce registration ID from requests since it is done by callers; the exception is org.springframework.security.saml2.provider.service.web.Saml2AuthenticationTokenConverter, which we introduce a registration resolver wrapper com.Strategy.auth.saml.response.SAMLSSORelyingPartyRegistrationResolver which resolve registration ID from request for Saml2AuthenticationTokenConverter, then delegate the task to SAMLRelyingPartyRegistrationResolverBean nameChangesmstrSamlProcessingFilterSAML bean with base class replaced by Spring Security SAML provider builtin class:

old: com.Strategy.auth.saml.response.SAMLProcessingFilter

new: org.springframework.security.saml2.provider.service.web.authentication.Saml2WebSsoAuthenticationFilterforwardedHeaderFilter
cookieProcessorFilter
clientIDFilter
redirectResponseFilterThese filters are defined in MainConfig.xml, some of which has the same name with filters defined in web.xml. They are renamed to avoid unexpected auto registration and duplicated filter names:

forwardedHeaderFilter → mstrForwardedHeaderFilter
cookieProcessorFilter → mstrCookieProcessorFilter
clientIDFilter → mstrClientIDFilter
redirectResponseFilter → mstrRedirectResponseFilter

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

Perform Namespace Changes

Update any import statements or other source code uses of EE API classes from the javax package to jakarta.
Here is an example to modify the import statement.
Before:


import javax.servlet.http.HttpServletRequest;

After:


import jakarta.servlet.http.HttpServletRequest;

This can be done with IntelliJ IDEA’s “Java EE to Jakarta EE“ tool which can be opened by clicking Refactor > Migrate Packages and Classes > Java EE to Jakarta. Go to Using IntelliJ IDEA's migration tool - JetBrains Guide for more steps.

After the migration, there are still classes in the javax.* namespace which is provided by Java SE. These are not affected by the Jakarta EE namespace migration, so stay as they are. Some examples are:
javax.annotation.processing.*
javax.crypto.*
javax.security.*
javax.sql.*
javax.transaction.xa.*
javax.xml.*
javax.swing.*
javax.management.*
javax.naming.*
javax.net.*

Review Spring Security XML Configurations for Bean Deprecation / Updates

Some changes are made on Spring Security XML configurations due to class deprecation / updates. Please review the below bean items and see if they are overwritten in customization. If true, corresponding change has to be made.

Changes shared by Strategy web/mobile and Library web

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

Changes only in Library web

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

samlAuthenticationRequestFactory

samlAuthenticationRequestContextConverter

Summary

With the preceding sections addressed, most of the blockers should be resolved. You can now compile source code, build the project, and deploy it on Tomcat 10 for validation.
However, there might still be third-party libraries lacking support for Jakarta EE 9, i.e. Axis2 . Here are some recommendations:

Explore alternative solutions.
Consider utilizing migration tools like gradle-jakartaee-migration-plugin .

Comment

0 comments

Details

Knowledge Article

Published:

April 25, 2024

Last Updated:

June 7, 2024