Set 'Secured' property for Form authentication cookies #12450
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #12441
@stuartwdouglas we do not set a same-site cookie in OIDC but only a
Secured
property, this should resolve the issue as OIDC users have never reported it.The test does not use HTTPS (I believe it is not possible with RestAssured in Quarkus at the moment), so it just verifies that this property is disabled for non-SSL