8000 Default to num_owners=2 when the persistent-user-sessions feature is disabled · Issue #40472 · keycloak/keycloak · GitHub
[go: up one dir, main page]

Skip to content

Default to num_owners=2 when the persistent-user-sessions feature is disabled #40472

Closed

Description

@ryanemerson

Description

In the documentation we advised users who use volatile sessions, i.e. persistent-user-sessions feature is disabled, to explicitly configure num_owners > 1 to prevent data loss. However, by default num_owners=1 and changing this value requires users to provide a custom Infinispan .xml file.

Instead, we should automatically configure num_owners = 2 if the user has not explicitly configured this value and if no shared persistence store exists. This will prevent users accidentally providing an unsafe configuration with volatile sessions.

Discussion

No response

Motivation

No response

Details

No response

Activity

  1. self-assigned this
    on Jun 13, 2025
  2. changed the title [-]Prevent num_owners=1 when the persistent-user-sessions feature is disabled[/-] [+]Default to num_owners=2 when the persistent-user-sessions feature is disabled[/+] on Jun 13, 2025
  3. added a commit that references this issue on Jun 13, 2025
    ab48883
  4. added
    area/infinispanInfinispan — distributed caches, clustering, JGroups, cross-site replication
    and removed on Jun 13, 2025
  5. added a commit that references this issue on Jun 16, 2025
    78f575b
  6. ahus1 commented on Jun 16, 2025

    @ahus1
    Member

    @ryanemerson, @mhajas, @pruivo - I would like to see this change backported to 26.2 as we're about to support RHBK 26.2 for another 10 months, and not everyone has migrated yet.

    Happy to hear your thoughts in favor or against this suggestion, or if you are neutral.

    Adding the backport label while we discuss this one.

    Similar to #40483 which is a follow-up.

  7. added a commit that references this issue on Jun 16, 2025
    4e5f7c6
  8. pruivo commented on Jun 16, 2025

    @pruivo
    Member
  9. ryanemerson commented on Jun 16, 2025

    @ryanemerson
    ContributorAuthor

    + .5 🙂

    I think it makes sense from a RHBK perspective. It will result in a change of behaviour for upstream 26.2 users, so if anybody has (incorrectly) relied on num_owners=1, they might be in for a surprise with the next patch release.

  10. ahus1 commented on Jun 17, 2025

    @ahus1
    Member

    @ryanemerson - as discussed in our team meeting yesterday, please create a backport. Thanks!

  11. added a commit that references this issue on Jun 20, 2025
    ebef702
  12. added a commit that references this issue on Jun 20, 2025
    8A8A
    87f2566
  13. added a commit that references this issue on Jan 19, 2026
    d4a3d5f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    0