Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Since property 'live.users.enabled' is deprecated, is there a replacement for managing session concurrency?

Written By

Jose L. Bango

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • The property live.users.enabled is required to manage simultaneous user logins via the auth.simultaneous.logins property.
  • However, live.users.enabled has been marked as deprecated for a while.
  • This raises questions about whether it is safe to use for managing session concurrency and if there is a replacement.

Environment

  • Liferay DXP 2025.Q1

Resolution

  • Currently, there is no out-of-the-box alternative to using the live.users.enabled property for managing simultaneous logins. It is required for the auth.simultaneous.logins property to function.
  • The decision to mark this property as deprecated was made in the past due to its connection with other features like "Live Users" and "Session Tracker".
  • There are no immediate plans to remove this property. Any future removal would only happen after a detailed analysis and with a guaranteed alternative for managing simultaneous logins.
  • In addition, if that removal ever happens, auth.simultaneous.logins should be able to provide the same behavior, or an alternative method would be provided.
  • This topic will be analyze in the following Spike:
    • LPD-57219 Define a plan for ensuring that the handling of simultaneous logins keeps working
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?