[
https://issues.apache.org/jira/browse/JCLOUDS-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494961#comment-14494961
]
Daniel Broudy commented on JCLOUDS-683:
---------------------------------------
Your understanding is correct. The oauth api implements JWT flow and this is a
generic flow.
I found the following link very helpful in describing how OAuth V2 works incase
anyone else out there is looking for resources:
https://developers.google.com/identity/protocols/OAuth2ServiceAccount
One part that may be google specific is the ReadOrWriteScopes.forRequest
implemented in OAuthScopes.java
This method includes the logic for determining what scopes to attach based on
the request method.
Side question:
Im wondering what purpose the @Authorization annotation serves.
> Promote oauth API
> -----------------
>
> Key: JCLOUDS-683
> URL: https://issues.apache.org/jira/browse/JCLOUDS-683
> Project: jclouds
> Issue Type: Task
> Components: jclouds-core, jclouds-labs-google
> Affects Versions: 2.0.0
> Reporter: Jeremy Daggett
> Assignee: Chris Custine
> Priority: Trivial
>
> Promote the oauth API to the main jclouds/jclouds repo so that other
> apis/providers can leverage it.
> Original email thread:
> http://markmail.org/search/?q=jclouds+list%3Aorg.apache.jclouds.dev+OAuth#query:jclouds%20list%3Aorg.apache.jclouds.dev%20OAuth%20order%3Adate-backward+page:1+mid:wc3th3fantvxy6zy+state:results
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
