[
https://issues.jboss.org/browse/TEIID-3617?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3617:
---------------------------------------
Since a user's identity is vdb / security-domain dependent there isn't a simple
notion of identity at a system level. You'd have to have id's that are qualified
by the security domain - user@domain and/or specify the vdb/version. Also configuration
down to a transport level may considered optional - that is since there is now just a
single session service, it doesn't need to be specific to jdbc/pg/etc.
Having this as part of the vdb / vdb.xml is better encapsulated, but makes it much more
difficult to manage. We do have logic that allows for updates to the deployed vdb.xml,
like the connection-type property, but there's currently no good way to export that
I'm aware of. At worst we could just expect someone to add restrictions to the
vdb.xml and redeploy.
Let's determine if it makes sense to have this at a vdb level (either specified as
part of the system level restriction, or in the vdb.xml) and what that would imply in
terms of management.
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)