• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Devaka Cooray
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Junilu Lacar
  • paul wheaton
  • Paul Clapham
Saloon Keepers:
  • Piet Souris
Bartenders:

Update to Spring Boot 2.7.5 with Spring Security 5.7.4

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Howdy,

I am attempting to update my enterprise level application to Spring Boot 2.7.5 with Spring Security 5.7.4 and I am running into a couple different CORS issues. The first is a 302 Found redirect when trying to use any API endpoints, I have not experienced this in a week so maybe it's been resolved but I'm not sure, and the other is a 403 invalid preflight with missing Access-Control-Allow-Origin header which I am currently dealing with.

The reason for the update is because sometimes when deploying to a Tomcat 9 server, the created WAR files either do not even run, or they say they are running but none of the API endpoints are exposed. I'm beginning to think the update won't have an impact on them.

How would I configure my SecurityConfig class to utilize my custom filters and overcome the CORS issues I am dealing with?

SecurityConfig implementation


Custom CORS Filter
 
reply
    Bookmark Topic Watch Topic
  • New Topic