[
https://issues.apache.org/jira/browse/JCLOUDS-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492133#comment-14492133
]
Ignasi Barrera commented on JCLOUDS-683:
----------------------------------------
I started to look at this, and after a first look to the code, I think it
should be able to promote it without changes. Correct me if I'm wrong, but it
implements the JWT flow to get the bearer token, and then the autentication
using that token.
Both are standard flows, and for example the Bearer token auth is all what we
need to use the OAuth code in the DigicalOcean API v2. It should already work
without changing the code. Regarding the other flow, I assume it is also
standard and not particular to GCE. Other OAuth v2 flows can be implemented the
same way once we have some provider that needs them.
[~broudy] is my understanding on the current status of the oauth api correct?
> 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)
