[
https://issues.jboss.org/browse/TEIID-4552?page=com.atlassian.jira.plugin...
]
Jan Stastny commented on TEIID-4552:
------------------------------------
I believe that has to be a change in the login module too, to support refresh_token-less
use cases.
I remember that at least LinkedIn and Strava social sites, don't use refresh_token at
all. I think they use long-lasting access_token instead.
Sort of a workaround would be to allow configuring access_token directly in the
resource-adapter's security domain. Is this something we want, or are there some
concerns?
To illustrate what I am talking about look at this diff:
https://github.com/teiid/teiid/compare/master...jstastny-cz:oauth2-access...
The idea was to bypass refreshing the token, if access_token is provided from the
configuration of security-domain.
Missing support for connection to Facebook via OAuth 2
------------------------------------------------------
Key: TEIID-4552
URL:
https://issues.jboss.org/browse/TEIID-4552
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 8.12.5
Reporter: Lucie Fabrikova
Assignee: Kylin Soong
Fix For: 9.3
Attachments: facebook3-vdb.xml, query, server.log, standalone.xml,
teiid-oauth-util.sh-output
I would like to connect to facebook resource adapter and configure OAuth 2 security
domain for it; I used teiid-oauth-util.sh to generate the security domain (see
attachment). Facebook doesn't support refresh tokens and in the generated code is
refresh token's value "null".
If I try to execute VDB with source pointing to such resource adapter I get error:
ERROR [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue13) Connector worker process
failed for atomic-request=Gapuea1/NRcn.6.3.0:
org.apache.cxf.rs.security.oauth2.provider.OAuthServiceException
(see server.log, facebook-vdb.xml, standalone.xml)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)