[teiid-issues] [JBoss JIRA] (TEIID-4826) OAuth2 add option to set access_token directly in login module

[Ramesh Reddy (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-4826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Reddy resolved TEIID-4826.
---------------------------------
    Fix Version/s: 9.3
         Assignee: Jan Stastny  (was: Steven Hawkins)
       Resolution: Done
           Labels: Alpha2  (was: )


> OAuth2 add option to set access_token directly in login module
> --------------------------------------------------------------
>
>                 Key: TEIID-4826
>                 URL: https://issues.jboss.org/browse/TEIID-4826
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: Server
>    Affects Versions: 9.3
>            Reporter: Jan Stastny
>            Assignee: Jan Stastny
>              Labels: Alpha2
>             Fix For: 9.3
>
>
> OAuth2 login module expects that auth service issues a 'refresh_token' together with an access_token. Then it can be used together with 'access_token_uri' to get a valid access_token automatically.
> Still this prevents Teiid from being configured for such OAuth2 implementations, that don't provide the refresh_token.
> One option how to workaround this inconsistency in OAuth2 service implementations is to provide option to set the access_token directly in a login-module. This would resolve the issue for never expiring or long-lasting access_token.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)