[
https://issues.jboss.org/browse/TEIID-4561?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-4561:
-------------------------------------
There is no KeycloakLoginModule used, if one exists I am not sure what it does (yet).
Also, so far we have only used Keycloak for OAuth2, SAML purposes only, not general
authentication framework, that role is still done by jboss pickletlink.
There will be a Subject when OAuth20LoginModule is used to secure a
data source on the call to the data source. Are you talking about a different point in the
flow?
no, I am saying a new Subject is created here, not passed from another layer,
and access token is added as a private credential
Deprecate the PassthroughIdentityLoginModule
--------------------------------------------
Key: TEIID-4561
URL:
https://issues.jboss.org/browse/TEIID-4561
Project: Teiid
Issue Type: Quality Risk
Components: Server
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.2
The delegation capability of the PassthroughIdentityLoginModule can be associated with
the underlying OAuth10/20 login modules (similar to the delegationCredential behavior of
the KerberosLoginModule). Also the OAuthCredentialContext should be changed to use the
Subject private credentials rather than a ThreadLocal.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)