-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: remove login session cookie #3667
Conversation
0204c18
to
4855724
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #3667 +/- ##
==========================================
- Coverage 76.15% 75.90% -0.26%
==========================================
Files 133 134 +1
Lines 10044 10075 +31
==========================================
- Hits 7649 7647 -2
- Misses 1878 1912 +34
+ Partials 517 516 -1 ☔ View full report in Codecov by Sentry. |
802ac23
to
d5f8aaf
Compare
ea1eb62
to
a9f03dc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First pass - this looks good. Let's see what the CI has to say!
I assume the cookie is still going to be set after the consent challenge has been accepted, correct? It's simply not needed during the login/consent dance (which was previously the case)
a9f03dc
to
dd52765
Compare
The CI is very excited about this change ;)
Yes, the final session cookie gets written here: hydra/consent/strategy_default.go Lines 480 to 492 in e2922c4
|
Related issue(s)
Checklist
introduces a new feature.
contributing code guidelines.
vulnerability. If this pull request addresses a security vulnerability, I
confirm that I got the approval (please contact
[email protected]) from the maintainers to push
the changes.
works.
Further Comments