vyommani commented on code in PR #1200:
URL: https://github.com/apache/ranger/pull/1200#discussion_r3902678126
##########
security-admin/src/main/resources/conf.dist/ranger-admin-default-site.xml:
##########
@@ -178,6 +178,16 @@
<name>ranger.admin.login.autolock.maxfailure</name>
<value>5</value>
</property>
+ <property>
+ <name>ranger.session.limit.concurrency</name>
Review Comment:
Could this description call out two things explicitly, so operators aren't
surprised:
1. This limit is enforced per Ranger Admin node's in-memory session list,
not cluster-wide in an HA/load-balanced deployment a user can hold up to this
many sessions on *each* node.
2. Beyond the plugin/tag/role/policy download URLs, any authenticated
request (including REST/API calls under the same login ID, e.g. scripted
`RangerClient` usage) counts toward this limit, not just browser UI sessions.
Both are non-obvious from the property name
(`ranger.session.limit.concurrency`) and could otherwise surprise someone
tuning this in a cluster or with automation running under a shared account.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
