[
https://issues.jboss.org/browse/TEIID-3669?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3669:
---------------------------------------
Without other changes, this will give us a single default security-domain(s). There would
still be the ability to configure the security-domain per vdb, but not per transport.
This seems like an issue when expecting an application level security domain with
pass-through and a different gss security domain.
Look at consolidating to a single session service
-------------------------------------------------
Key: TEIID-3669
URL:
https://issues.jboss.org/browse/TEIID-3669
Project: Teiid
Issue Type: Quality Risk
Components: Server
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.0
We should consider moving back to a single session service in Teiid 9 as most of the
constraints will be specified on a vdb basis (such as security domain, auth type, etc.)
and the separation in the session service causes issues with sessions originating in
different transports - TEIID-3663
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)