You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The expectation is that requests for "/B.html" will have the XFRAME header disabled AND not require authentication, and all other request would have the default headers and require authentication.
In fact, requests for "/B.html" do have the XFRAME header disables (as expected) but require authentication.
It appears that the filter that does the authenication applies the rules for both sections, so that the first rule permits access and the second rule requires authentication, rather than only applying the rules from the relevant HTTP element
The text was updated successfully, but these errors were encountered:
cartbar
changed the title
Using XML configuration, separate HTTP element share authentication
Using XML configuration, separate HTTP elements share authentication
Feb 26, 2025
I created an XML file to configure the Spring Security in my application:
The expectation is that requests for "/B.html" will have the XFRAME header disabled AND not require authentication, and all other request would have the default headers and require authentication.
In fact, requests for "/B.html" do have the XFRAME header disables (as expected) but require authentication.
It appears that the filter that does the authenication applies the rules for both sections, so that the first rule permits access and the second rule requires authentication, rather than only applying the rules from the relevant HTTP element
The text was updated successfully, but these errors were encountered: