[teiid-issues] [JBoss JIRA] (TEIID-3763) WS connector oauth security setting not work in Embedded

[Ramesh Reddy (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119977#comment-13119977 ] 

Ramesh Reddy commented on TEIID-3763:
-------------------------------------

OAuth10LoginModule and OAuth20LoginModule do the job of getting the "AccessToken" based on the "RefreshToken" obtained by the teiid-oauth-util.sh. So, Yes they are needed, so are the other properties. Look inside the "OAuth20CredentialImpl" and "OAuth10CredentialImpl" classes.

teiid-oauth-util.sh "only" gets the "RefreshToken", that is does not the complete security. Also, the "AccessToken" does expire and can be revoked any time, in those situations the LoginModule re-negotiates a new AccessToken.

As per per your UI comment, I have not thought about it yet. Yes it is already supported in WSManagedConnectionFactory, I am not sure what you mean by that comment.

As per IronJacmar, I am not sure how that integrates, so I can not comment right now.

> WS connector oauth security setting not work in Embedded
> --------------------------------------------------------
>
>                 Key: TEIID-3763
>                 URL: https://issues.jboss.org/browse/TEIID-3763
>             Project: Teiid
>          Issue Type: Bug
>          Components: Misc. Connectors
>    Affects Versions: 8.12
>            Reporter: Kylin Soong
>             Fix For: 8.12.x
>
>         Attachments: jca-ra-outbound.png
>
>
> 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)