8000 ClientSession timestamp not updated in the database by pruivo · Pull Request #42518 · keycloak/keycloak · GitHub
[go: up one dir, main page]

Skip to content

ClientSession timestamp not updated in the database - #42518

Merged
ahus1 merged 3 commits into
keycloak:mainfrom
pruivo:t_42012
Sep 10, 2025
Merged

ahus1 merged 3 commits into
keycloak:mainfrom
pruivo:t_42012

Conversation

@pruivo
@pruivo pruivo commented Sep 10, 2025
Copy link
Copy Markdown
Member

Closes #42012

Closes keycloak#42012

Signed-off-by: Pedro Ruivo <1492066+pruivo@users.noreply.github.com>
@pruivo
pruivo requested a review from ahus1 September 10, 2025 14:32
@pruivo
pruivo commented Sep 10, 2025
Copy link
Copy Markdown
Member Author

@ahus1 let me know what you think.

@ahus1 ahus1 self-assigned this Sep 10, 2025
ahus1
ahus1 previously approved these changes Sep 10, 2025
@ahus1 ahus1 left a comment
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the quick turnaround!

Signed-off-by: Pedro Ruivo <1492066+pruivo@users.noreply.github.com>
@pruivo
pruivo commented Sep 10, 2025
Copy link
Copy Markdown
Member Author

@ahus1 I've just pushed another commit to check for nulls. Please review.

ahus1
ahus1 previously approved these changes Sep 10, 2025
Signed-off-by: Pedro Ruivo <1492066+pruivo@users.noreply.github.com>
@pruivo
pruivo marked this pull request as ready for review September 10, 2025 17:24
@pruivo
pruivo requested review from a team as code owners September 10, 2025 17:24
@ahus1
ahus1 merged commit 8567eec into keycloak:main Sep 10, 2025
@pruivo
pruivo deleted the t_42012 branch September 10, 2025 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Client session timestamp not updated in the database if running multiple nodes

2 participants

0