Repository navigation
Conversation
niemyjski
force-pushed
the
issue/password-check-capacity
branch
from
October 13, 2026 02:39
215c37e to
d8cefff
Compare
niemyjski
force-pushed
the
issue/current-user-token-state
branch
2 times, most recently
from
October 13, 2026 02:41
76e8282 to
229c8d7
Compare
niemyjski
force-pushed
the
issue/password-check-capacity
branch
from
October 13, 2026 02:41
d8cefff to
79578cc
Compare
niemyjski
force-pushed
the
issue/current-user-token-state
branch
from
October 13, 2026 02:58
229c8d7 to
1ff975e
Compare
niemyjski
force-pushed
the
issue/password-check-capacity
branch
from
October 13, 2026 02:58
79578cc to
121c87b
Compare
niemyjski
force-pushed
the
issue/current-user-token-state
branch
from
October 13, 2026 03:05
1ff975e to
5601ad2
Compare
niemyjski
force-pushed
the
issue/password-check-capacity
branch
from
October 13, 2026 03:05
121c87b to
3bdef04
Compare
niemyjski
added this pull request to stack #2659
October 13, 2026 03:05
niemyjski
removed this pull request from stack #2659
October 13, 2026 12:26
niemyjski
force-pushed
the
issue/password-check-capacity
branch
from
October 13, 2026 12:26
3bdef04 to
e42d7f5
Compare
niemyjski
force-pushed
the
issue/current-user-token-state
branch
from
October 13, 2026 12:26
5601ad2 to
609782b
Compare
niemyjski
changed the base branch from
issue/password-check-capacity
to
issue/user-session-generation
October 13, 2026 12:27
niemyjski
force-pushed
the
issue/current-user-token-state
branch
2 times, most recently
from
October 13, 2026 13:33
f610a5c to
5494433
Compare
|
niemyjski
force-pushed
the
issue/current-user-token-state
branch
from
October 13, 2026 13:55
5494433 to
137f849
Compare
niemyjski
force-pushed
the
issue/user-session-generation
branch
3 times, most recently
from
October 14, 2026 02:38
9593b05 to
2ef6152
Compare
niemyjski
force-pushed
the
issue/current-user-token-state
branch
2 times, most recently
from
October 14, 2026 02:50
2128046 to
a3a453e
Compare
niemyjski
force-pushed
the
issue/user-session-generation
branch
from
October 14, 2026 03:03
4222af7 to
a178e7b
Compare
niemyjski
force-pushed
the
issue/current-user-token-state
branch
from
October 14, 2026 03:03
a3a453e to
21eef5f
Compare
This was referenced Oct 14, 2026
Merged
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This draft checks stored user-session and OAuth token state after logout or revocation. It now depends directly on #2627 rather than inheriting the unrelated password and concurrency proposals.
BLOCKER: the current approach can read a user token twice on a cache miss, and uncached OAuth application lookups can trigger Elasticsearch refreshes per request. A bounded, high-throughput lookup contract and corresponding regression coverage are required before merging.
Validation: production changes rebased onto the updated session-generation implementation. Endpoint runtime verification remains blocked by Aspire/DCP startup. This PR is not ready to merge.