Spring security customizations related to OECORSFilter transferred from OpenEdge 12.2 to OpenEdge 12.8 are preventing the OpenEdge 12.8 pasoe instance from starting

Nov 13, 2025
Knowledge

Title

URL Name

spring-security-customizations-related-to-oecorsfilter-transferred-from-openedge-12-2-to-openedge-12-8-are-preventing-the-openedge-12-8-pasoe-instance-from-starting

Article Number

000294120

Environment

Product: OpenEdge Version: 12.8 OS: All Supported Platforms

Question/Problem Description

Spring security customizations related to OECORSFilter transferred from OpenEdge 12.2 to OpenEdge 12.8 are preventing the OpenEdge 12.8 pasoe instance from starting

Steps to Reproduce

Clarifying Information

In OpenEdge 12.8, the spring security files needed to customize spring security for a particular pasoe instance were copied using the steps from the option 2) from the following article:

https://community.progress.com/s/article/the-spring-security-template-loginmodel-xml-files-are-missing-in-deployed-pasoe-web-inf-spring-folders-since-openedge-version-12-3

Error Message

2025-11-06T11:32:07.010+01:00 WARN [Catalina-utility-1] - c.p.a.s.s.OEXmlWebApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.security.filterChains': Cannot resolve reference to bean 'org.springframework.security.web.DefaultSecurityFilterChain#2' while setting bean property 'sourceList' with key [2] 2025-11-06T11:32:07.015+01:00 ERROR [Catalina-utility-1] - o.s.web.context.ContextLoader - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.security.filterChains': Cannot resolve reference to bean 'org.springframework.security.web.DefaultSecurityFilterChain#2' while setting bean property 'sourceList' with key [2] ... Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.security.web.DefaultSecurityFilterChain#2': Cannot resolve reference to bean 'OECORSFilter' while setting constructor argument with key [2] ... Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'OECORSFilter' defined in URL [file:C:/thePasoeInstanceFolder/webapps/theWebAppName/WEB-INF/spring/authFilters.xml]: Failed to instantiate [com.progress.appserv.services.security.OECORSFilter]: No default constructor found

Defect Number

Enhancement Number

Cause

Spring security customizations related to OECORSFilter need a slightly different syntax in the higher version of spring security used by pasoe in OpenEdge 12.8

Resolution

In the file:

${catalina.base}/webapps/${oeabl.webapp.name}/WEB-INF/spring/authFilters.xml

change the following configuration used in OpenEdge 12.2:

    <b:bean id="OECORSFilter"
             class="com.progress.appserv.services.security.OECORSFilter" >
             <b:property name="responseHeaders" value="${OECORSFilter.responseHeaders}" />
             <b:property name="allowAll" value="${OECORSFilter.allowAll}" />
             <b:property name="allowDomains" value="${OECORSFilter.allowDomains}" />
             <b:property name="allowSubdomains" value="${OECORSFilter.allowSubdomains}" />
             <b:property name="allowMethods" value="${OECORSFilter.allowMethods}" />
             <b:property name="messageHeaders" value="${OECORSFilter.messageHeaders}" />
             <b:property name="supportCredentials" value="${OECORSFilter.supportCredentials}" />
             <b:property name="maxAge" value="${OECORSFilter.maxAge}" />
    </b:bean>

into the following configuration for OpenEdge 12.8

    <b:bean id="OECORSFilter"
            class="com.progress.appserv.services.security.OECORSFilter" >
      <b:constructor-arg ref="corsSource"/>
      <b:property name="allowAll" value="${OECORSFilter.allowAll}" />
    </b:bean>                
    
    <b:bean id="corsSource" class="org.springframework.web.cors.UrlBasedCorsConfigurationSource">
      <b:property name="corsConfigurations">
        <b:map>
          <b:entry key="/**">
            <b:bean class="com.progress.appserv.services.security.OECorsConfiguration">
              <b:property name="responseHeaders" value="${OECORSFilter.responseHeaders}" />
              <b:property name="allowDomains" value="${OECORSFilter.allowDomains}" />
              <b:property name="allowSubdomains" value="${OECORSFilter.allowSubdomains}" />
              <b:property name="allowMethods" value="${OECORSFilter.allowMethods}" />
              <b:property name="messageHeaders" value="${OECORSFilter.messageHeaders}" />
              <b:property name="supportCredentials" value="${OECORSFilter.supportCredentials}" />
              <b:property name="maxAge" value="${OECORSFilter.maxAge}" />
              <b:property name="allowAll" value="${OECORSFilter.allowAll}" />
            </b:bean>
          </b:entry>
        </b:map>
      </b:property>
    </b:bean>

Workaround

Notes

Keyword Phrase

Last Modified Date

11/13/2025 2:26 PM

Spring security customizations related to OECORSFilter transferred from OpenEdge 12.2 to OpenEdge 12.8 are preventing the OpenEdge 12.8 pasoe instance from starting

Files(0)

Was this article helpful?

Was this article helpful?

Spring security customizations related to OECORSFilter transferred from OpenEdge 12.2 to OpenEdge 12.8 are preventing the OpenEdge 12.8 pasoe instance from starting

Information

Related Articles