[
https://issues.jboss.org/browse/TEIID-2818?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2818:
-------------------------------------
This is most cryptic requirement I have seen. The [
OAuth|http://oauth.net/documentation/]
specification is extended to allow different types of GRANT types. They are
* JSON Web Token
* OAuth Assertions Framework
* SAML2 Bearer Assertion - for integrating with existing identity systems - TEIID-2819
* JWT Bearer Assertion - for integrating with existing identity systems
The first two Teiid does not need to support as they are *not* involving the
"delegation", the last two are the delegation models. I suspect this JIRA need
to be support of "JWT Bearer Assertion". If we are just want to deal with OAuth
and SAML TEIID-2819 is suffice.
Use Oauth SAML Grant Type
-------------------------
Key: TEIID-2818
URL:
https://issues.jboss.org/browse/TEIID-2818
Project: Teiid
Issue Type: Feature Request
Components: Server
Reporter: Van Halbert
Assignee: Ramesh Reddy
How to connect to underlying data sources on behalf of Oauth when user comes into
webservice with Oauth?
Use cases:
1 – client u/p sources: oauth/saml
2- client : oauth/saml sorces u/p, other
3 – client: Oauth/saml sources Oauth/saml (data sources are also secured by Oauth) –
3a) propogate sources and 3b – resolve new tokens for sources
Link:
http://www.layer7tech.com/tutorials/oauth-20-with-layer-7-gateways-tutori...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)