AGSEC-201/203: Move the OAuth2 configuration to aerogear.org #506
Conversation
abstractj
changed the title
|
The google description you have here only works for Android. If you take the one from here, that will work for all platforms Android, iOS and Windows. |
|
Google working with iOS is a bit more tricky, @edewit doc is good. |
@corinnekrych mind filing a separate JIRA / PR for this ? |
|
|
||
| * [Android client library](http://search.maven.org/#artifactdetails%7Corg.jboss.aerogear%7Caerogear-android-authz%7C2.0.0%7Caar) | ||
| * [iOS client library](http://cocoapods.org/?q=aerogearoauth2) | ||
| * [Apache Cordova client library](https://github.com/aerogear/aerogear-oauth2-cordova/releases/tag/v1.0.2) |
There was a problem hiding this comment.
Let's use this link: http://plugins.cordova.io/#/package/org.jboss.aerogear.cordova.oauth2
Sounds good using that info from the cookbook. One question: Should the cookbook just than link to the site, for the setup ? I think it would make sense to have one, centralized configuration page. |
|
@matzew right, after this PR is merged we can update the cookbooks to point to the site |
|
awesome On Wed, Feb 25, 2015 at 9:24 AM, Erik Jan de Wit notifications@github.com
Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ |
|
@edewit I will do the changes suggested by you today @matzew Regarding the readme updates, that's was my plan after get some feedback here, anyways thanks @corinnekrych for creating those jiras. I created https://issues.jboss.org/browse/AGSEC-205 and attached the related Jiras there. I will review all the comments here this morning and update this PR. Thanks in advance for the feedback. |
|
cool beans! great seeing this initiative, @abstractj On Wed, Feb 25, 2015 at 10:23 AM, Bruno Oliveira notifications@github.com
Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ |
| * [AeroGear Two-Factor Authentication with OTP as Cordova Plugin](aerogear-cordova/AerogearCordovaOTP) | ||
|
|
||
| * OAuth2 | ||
| 1. [Basic steps](security/oauth2-basic-steps) |
There was a problem hiding this comment.
I would prefer something like Getting Started with various OAuth2 Providers (Basic Steps sounds too general imo)
There was a problem hiding this comment.
@lfryc that's the idea, be general, various OAuth2 providers is general in the same way. Most of the guides outside make use of this sentence.
There was a problem hiding this comment.
What about Getting Started with various OAuth2 Providers (Keycloak, Facebook, Google)?
I just didn't expect what that link opened, but we may reiterate later on overall structure.
There was a problem hiding this comment.
@lfryc We can always improve later, this is not something definitive. Also, with the new website we gonna have room enough to change. I think more important now is to see if the content looks good and later we can rearrange/move sections.
Additional authors: Petr Stribny <pstribny@redhat.com> Summers Pittman <secondsun@gmail.com> Bruno Oliveira <bruno@abstractj.org>
Additional authors: Matthias Wessendorf <matzew@apache.org> Christos Vasilakis <cvasilak@gmail.com> Daniel Passos <daniel@passos.me> Summers Pittman <secondsun@gmail.com> Bruno Oliveira <bruno@abstractj.org>
|
@edewit @corinnekrych updated. Let me know if anything is missing |
|
👍 like the blur you added on the google logged in use picture |
|
👍 |
|
Landed, thank you all |
This is just the start from the series of section for security, I prefer to deliver early and often instead of a gazillion of documentation to review.
To track all the items being created check AGSEC-200.
@danielpassos @matzew @lfryc @cvasilak @secondsun @edewit @corinnekrych you are all invited to review.
Keep in mind that the content will be moved gradually to the
new-designbranch and I also made sure to keep the ownership of the document.