OutSystems.com
My Platform
Community
Support
Training
Training
Guided Paths
Build an App
Training Planner
Courses
Developer Schools
Boot Camps
Certifications
Tech Talks
Documentation
Documentation
Overview
ODC
O11
Forums
Forge
Get Involved
Get Involved
Jobs
Ideas
Members
Mentorship
User Groups
Downloads
Search in OutSystems
Log in
Sign Up
Community
›
Forge
›
Assets list
›
Google Services OAuth2
João Ventura Abreu
Created on 20 October 2017
Login to follow
Google Services OAuth2
Stable version
1.0.5
(Compatible with
OutSystems 11
)
Other versions available for 10 and Older
Uploaded on
09 July 2020
by
Try now
Traditional web
4.3
(8 ratings)
3 reviews
1014
58
Overview
Reviews
Versions
Documentation
There's no documentation for this asset yet
Support
Google Services OAuth2
Try now
Reviews
Sort by:
Newest
Newest
Oldest
Highest rating
Lowest rating
5 star
4
0
Reviews |
4
Ratings
4 star
2
1
Review |
2
Ratings
3 star
2
1
Review |
2
Ratings
2 star
0
0
Reviews |
0
Ratings
1 star
0
0
Reviews |
0
Ratings
8
Ratings
4.3
Average rating
3
Reviews
by
2020-03-24
in version 1.0.3
The current version didn't work for me. You should add a separate REST API for the Google People API: https://people.googleapis.com. Also add the query parameter 'personFields' as required parameter to the Google People API.
by
2019-11-25
in version 1.0.3
Google APi methods were updated , so it is necessary to update GetMe url.
My suggestion is to change to People API as recommended by Google.
Thank you
by
2019-01-02
in version 1.0.2
A demo would be greatfull to integrate this component with less effort.
Things that could be improved:
- The example on API AccessTokenGet must have all inputs on the same line, to test this on the fly;
- A first screen, before the google authentication page, to handle with the construction of URL* with an input with where we want be redirect after the user accepts the authentication.
- The preparation of AuthorizationResponsePage has a ForEach that splits the state by demiliter "&". When the callback URL has inputs, how this can be handled?
* In my case, the URL is structured with the following example:
"https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=#client_id#&scope=#scope#&state=#state#&redirect_uri=#redirect_uri#&approval_prompt=force&access_type=offline"
Replacing the #client_id#, #scope#, #state# and #redirect_uri# for another values.
Loading...
Loading