The process of Google Sign-in in your marketplace is really straightforward, however, there are several technical-looking steps that you need to complete before this is ready. If you follow all the steps you should be able to complete this without any issue.
Note: Google's interface is subject to change. If you encounter any inconsistencies with this step-by-step guide, please contact Sharetribe's Support team and we will be happy to assist.
In order to configure Google Sign-in in your marketplace, you need to do two things:
Create a Google Cloud development project
Connect that project to your marketplace through Console.
Create and set up a Google Sign-In Project
Log in with your Google account (you may have to register as a developer if you don't have a Google developer account already).
Click the "Select a project" button on the top bar.
If you already have a project, the selector will display the name of your project.
When the pop-up opens click the "New project" button on the top right corner.
Name your Project (for example your marketplace name) and click "Create".
Go to the "OAuth consent screen" page e.g. from the left side menu.
Once there, select "External" as a User type and click "Create".
Fill in the required fields:
You need to add the App name and user support email for your app and the developer contact info (you should use your own email).
You can add an App logo, App's home page, privacy policy and terms of service links, but these are not mandatory (if you had a logo, you will have to go through an extra verification step when publishing).
Add your domain as an "Authorized domain" (just the domain without
https://)Add your email as the "Developer contact information".
Click "Save and continue"
There isn't anything to add to "Scopes", so you can just click "Save and continue".
There isn't anything to add to "Test users", so you can just click "Save and continue".
Review things in "Summary" then click "Back to dashboard".
From the left sidebar go to the "Credentials" page.
Click "+ Create credentials" from the top of the page and select "OAuth Client ID".
In "Application type", choose "Web application". You can give it any name.
Under "Authorized JavaScript origins", click "ADD URI" and add your complete marketplace's URL with https and possibly www or the subdomain, without the trailing slash, e.g. "
https://www.example.com", "https://example.com", or "https://something.example.com".Under the "Authorized redirect URIs", click "ADD URI" and add your marketplace address as you added it above, but followed by
/api/auth/google/callback. e.g "https://www.example.com/api/auth/google/callback".Click "Create".
Take note of the values of your Client ID and Client Secret, you will need them to connect this app to your marketplace (if you close the modal, you can find them later).
Go back to "OAuth consent screen" and click "PUBLISH APP" under Publishing status and confirm.
Some helpful screenshots in case you get stuck.
Some helpful screenshots in case you get stuck.
Step 3 - Select a project
Step 6 - Go to the "OAuth consent screen" link
Steps 9 and 10 - Credentials
Steps 12-15 - Create OAuth client ID
Connect the Google Sign-In project to your marketplace
Click "+ Add a new client"
As the client name, type "Google Sign in".
As an identity provider choose "Google"
Add the Client ID and Client secret as noted in step 15 when creating the app.
If you forgot to take a note you can find them again by going to Google Cloud Console > Credentials > OAuth 2.0 Client IDs and clicking the app name
Click "Add client"
That's it!
Where to find the Client ID and Secret
Where to find the Client ID and Secret
Test it out
You should make sure that things work by testing your signup and login process with Google.