Quick Task: Restrict Number of Concurrent Sessions Per User

Published on 26 March 2019 in Administration - 1 minute read - Last modified on 04 February 2020

Hue administrators can restrict the number of concurrent sessions per user. The default value is 0 to represent no restrictions. In that case, a user can have as many simultaneous Hue sessions, i.e. logins, as he wishes. For security purposes, this can be restricted. When it is, normally the concurrent_user_session_limit is set to 1.

[desktop]
  
[[session]]
  
concurrent_user_session_limit=1
  

When concurrent_user_session_limit is set to 1 any session, i.e. on a different machine or browser, in excess of 1 is removed by eldest. If a user gets logged out automatically, then he or she can assume somebody else is logging in as his/her credential on a different machine.

Note:

  • Most of the browsers for example Chrome is sharing the same session between windows or tabs.
  • This feature is not for restricting how many queries user can submit to Hive/Impala. Instead, they should set the Hive/YARN and Impala resource management pools properly (at the query engine, not the clients like Hue).

  • comments powered by Disqus

    More recent stories

    23 June 2020
    Monitoring Hue activity with Grafana Dashboards
    Read More
    22 June 2020
    Automated checks for JavaScript modules compatible licenses and non absolute paths with Continuous Integration
    Read More
    19 May 2020
    How to grant Ranger permissions for a new user on a Secure Cluster
    Read More