[
https://issues.jboss.org/browse/TEIID-3763?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3763:
-------------------------------------
The "Subject" is set in higher order of calling thread's context, thus
Managed Connection receives it. Setting them directly on Managed Connection is not correct
for pass-through scenarios.
The resource adapters are designed for JEE environments, especially for JBoss EAP. When
resource-adapter connections are selected for execution, the thread context happens
through JEE mechanics. That said, usage of them directly in "Embedded" as is
not appropriate as is in all situations. We need to think, if/how we need to
package/utilize differently in embedded scenario.
WS connector security setting not work in Embedded
--------------------------------------------------
Key: TEIID-3763
URL:
https://issues.jboss.org/browse/TEIID-3763
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 8.13
Reporter: Kylin Soong
Assignee: Steven Hawkins
Fix For: 8.13
In WSConnectionImpl setDispatchProperties setting depend on Security Subject:
{code}
else if (this.mcf.getAsSecurityType() == WSManagedConnectionFactory.SecurityType.OAuth)
{
Subject subject = ConnectionContext.getSubject();
if (subject != null) {
}
...
}
{code}
Note if run WS connector with security in Embedded, ConnectionContext.getSubject() return
null, the cause exception throw.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)