[
https://jira.jboss.org/jira/browse/TEIID-863?page=com.atlassian.jira.plug...
]
Ramesh Reddy resolved TEIID-863.
--------------------------------
Resolution: Done
Credential map based authentication at the connectors is removed. Now, if they need such
mechanism, connectors can to define their own 'security-domain', however it is not
clear as to how user can authenticate both Teiid level security-domain as well as
connector level. Also, need to investigate if JBoss supports the connection pools
segregation based on logged in user. Since this issue applies at the "data
source", leaving this at the JBoss's current support on this feature.
Trusted Payload still exists in the current code, as it also used to send hints in the
source level queries. However using this as the authentication payload is no longer
valid.
Remove Trusted payload, credential map for authenticating connector
sources
---------------------------------------------------------------------------
Key: TEIID-863
URL:
https://jira.jboss.org/jira/browse/TEIID-863
Project: Teiid
Issue Type: Sub-task
Components: Misc. Connectors
Affects Versions: 7.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 7.0
With TEEID-833 the engine will be deployed to a container and TEIID-199 implements the
JAAS based authentication. In the container environment the security credentials are
passed contextually to the working thread where they can be accessed. So, the custom home
grown solutions like trusted payload and credential mapping are no longer needed.
Make sure that "ConnectorContext" exposes the necessary information for the
security.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira