[
https://issues.jboss.org/browse/TEIID-3617?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3617:
-------------------------------------
Since Teiid does not have sessions scoped at system level, it seems verbose to include the
configuration to be at system level. There are also couple different issues when defining
at system level.
1. The configuration needs to include per vdb and user. As user count is kept only at VDB
scoped.
2. The security domain is unknown to the system, thus name of the user needs to be fully
scoped as "user@teiid-security" thus complicating the issue. If the user changes
the security-domain at VDB level, the setting in the system will be out of date.
So, it is recommended that to put this configuration at vdb level in the vdb.xml file,
then the configuration is scoped to the VDB. This will resolve above two issues. However
1. The issue here is with the updatability of configuration at runtime. Currently there
is limited support to update vdb.xml like we do in the change "connection-type",
but the issue raised here is about migration. However, the migration can be looked as
orthogonal issue, as we have that in either case to resolve.
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)