feat: add config parameter to redeclare same site cookie setup - #38458
Conversation
|
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
ded2870 to
63c3bc8
Compare
|
This will be docs relevant, pls do not forget to file a docs issue for a |
63c3bc8 to
f708e60
Compare
f708e60 to
2625377
Compare
|
@micbar pr is ready to be merged and released |
|
@DeepDiver1975 I know you don´t like it, but pls do: #38458 (comment) Can you pls give more info what the values mean/do? EDIT: let me rephrase, what would be the impact to a non openid environment when using strict or lax compared to the existing setup like without this PR? |
|
the internet is full of explanation around this .... no need to duplicate this information. |
the default is 'strict' - same as before this pr - no no change in behavior. |
|
@mmattel Thanks for the commit. Waiting for CI |
|
Kudos, SonarCloud Quality Gate passed! |
Admin docu should make the connection from the error message "Unable to determine state" to the config setting "http.cookie.samesite" |
|
I added a link to the docs issue (owncloud/docs#3260 (comment)) where there is more information. If you agree we take a closer look on that link if the information provided satisfies the needs and in case not, we have to ask @DeepDiver1975 for an in depth input. |
|
On macOS Mojave 10.14.6 (Safari 12.1.2) the error persists, see Confirmed fixed on macOS BigSur 11.1 and 11.2.3. |
Description
In case of openid redirect the cookie samesite strict or lax are not working.
Use:
to choose a different setup
Related Issue
How Has This Been Tested?
Types of changes
Checklist: