[
https://issues.jboss.org/browse/TEIID-3617?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3617:
-------------------------------------
why authentication-max-sessions-allowed can add as a attribute, and
authentication-max-sessions-allowed-per-user can't?
Because "authentication-max-sessions-allowed" is total number of sessions that
are allowed across all VDBs and across all the users. The default there is 10,000, not
1000. We can't have "authentication-max-sessions-allowed-per-user" because,
we want to keep this scoped to VDB. If we remove that requirement, then what you are
proposing can be allowed. In order to allow, what you are asking the attribute needs to be
like
{code}
/subsystem=teiid:write-attribute(name=authentication-max-sessions-allowed-per-user,value="user1/vdbOne@teiid-security=25;user1/vdbTwo@teiid-security=35")
{code}
Now if I delete the vdbOne, I need to come here and clean up all these references, not to
mention scalablility of the issue. Are you sure if there are 10,000 users, that is
configuration option you will take? Central configuration needs to be something that can
apply to all the components in a system. Can't change just because a user is added, or
vdb is deployed etc.
Provide an option to Limit per user based connections
-----------------------------------------------------
Key: TEIID-3617
URL:
https://issues.jboss.org/browse/TEIID-3617
Project: Teiid
Issue Type: Feature Request
Components: Server
Reporter: Xian Liu
Assignee: Kylin Soong
Fix For: 9.1
we deploy teiid for users to get data, but some users will create many connections to
teiid and they are not necessary, I need to find a good way to limit each user account can
only get like 50 connections or so
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)