Skip to content

SAML2 not working on 9.0.0 #12563

@jcbsdev

Description

@jcbsdev

Describe the bug

We have our Artemis instance setup with SAML2 authentication. The upgrade to Artemis 9.0.0/Spring Boot 4/Spring Security 7 breaks the SAML2 setup as it is described in the documentation.

After the upgrade to 9.0.0 the application cannot start because Parameter 0 of method relyingPartyRegistrationResolver in de.tum.cit.aet.artemis.core.config.SAML2Configuration required a bean of type 'org.springframework.security.saml2.provider.service.registration.RelyingPartyRegistrationRepository' that could not be found.

After some research my understanding of the problem is that the auto-configuration through config files changed with Spring Security 7 and it needs to be adressed in the source code and not in the config files.

To Reproduce

  1. Setup an Artemis 8.x.x instance with SAML2 authentication.
  2. Upgrade the instance to 9.0.0
  3. The application cannot start, because of the SAML2 errors.

Expected behavior

The application should either be fixed/changed, so that it keeps working with the SAML2 configuration described in the documentation. Or the documentation should describe the new configuration which is needed for SAML2 authentication on Artemis 9.0.0.

Screenshots

No response

Which version of Artemis are you seeing the problem on?

9.0.0

What browsers are you seeing the problem on?

Firefox

Additional context

No response

Relevant log output

Apr 16 20:03:00 ls14-artemis-node1 java[441889]: 2026-04-16T20:03:00.921+02:00 ERROR 441889 --- [Artemis] [           main] t.s.DeferredServletContainerInitializers : Error starting Tomcat context. Exception: org.springframework.beans.factory.UnsatisfiedDependencyException. Message: Error creating bean with name 'metadata' defined in class path resource [de/tum/cit/aet/artemis/core/config/SAML2Configuration.class]: Unsatisfied dependency expressed through method 'metadata' parameter 0: Error creating bean with name 'relyingPartyRegistrationResolver' defined in class path resource [de/tum/cit/aet/artemis/core/config/SAML2Configuration.class]: Unsatisfied dependency expressed through method 'relyingPartyRegistrationResolver' parameter 0: No qualifying bean of type 'org.springframework.security.saml2.provider.service.registration.RelyingPartyRegistrationRepository' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {}
Apr 16 20:03:01 ls14-artemis-node1 java[441889]: 2026-04-16T20:03:01.010+02:00  WARN 441889 --- [Artemis] [           main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Unable to start web server
Apr 16 20:03:01 ls14-artemis-node1 java[441889]: 2026-04-16T20:03:01.025+02:00  INFO 441889 --- [Artemis] [           main] .s.b.a.l.ConditionEvaluationReportLogger :
Apr 16 20:03:01 ls14-artemis-node1 java[441889]: Error starting ApplicationContext. To display the condition evaluation report re-run your application with 'debug' enabled.
Apr 16 20:03:09 ls14-artemis-node1 java[441889]: 2026-04-16T20:03:09.712+02:00 ERROR 441889 --- [Artemis] [           main] o.s.b.d.LoggingFailureAnalysisReporter   :
Apr 16 20:03:09 ls14-artemis-node1 java[441889]: ***************************
Apr 16 20:03:09 ls14-artemis-node1 java[441889]: APPLICATION FAILED TO START
Apr 16 20:03:09 ls14-artemis-node1 java[441889]: ***************************
Apr 16 20:03:09 ls14-artemis-node1 java[441889]: Description:
Apr 16 20:03:09 ls14-artemis-node1 java[441889]: Parameter 0 of method relyingPartyRegistrationResolver in de.tum.cit.aet.artemis.core.config.SAML2Configuration required a bean of type 'org.springframework.security.saml2.provider.service.registration.RelyingPartyRegistrationRepository' that could not be found.
Apr 16 20:03:09 ls14-artemis-node1 java[441889]: Action:
Apr 16 20:03:09 ls14-artemis-node1 java[441889]: Consider defining a bean of type 'org.springframework.security.saml2.provider.service.registration.RelyingPartyRegistrationRepository' in your configuration.

Metadata

Metadata

Assignees

No one assigned

    Labels

    assessmentPull requests that affect the corresponding modulebugcommunicationPull requests that affect the corresponding modulecorePull requests that affect the corresponding module

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions