This configuration enables Single Sign-On (SSO), providing a smoother user experience, reducing registration friction, and improving conversion rates.
Prerequisites
Before getting started, make sure you have the following:
The final URL of your second-hand site (example:
https://secondhand.brand.com), which should already be configured before setting up SSOThe name of your second-hand site
The icon/logo of your second-hand site
Administrator access to your Google Cloud Console
Step 1: Create Your Google Cloud Project
Log in to the Google Cloud Console.
Click Select a Project, then New Project.
Enter a project name, select an organization if required, and click Create.
Once the project has been created, select it from the project list.
This project will be used to manage your Google authentication configuration.
Step 2: Enable the Google OAuth API
In the console, go to APIs & Services → Library.
Search for and select the Google OAuth 2.0 API.
Click Enable.
This API is required to allow authentication through Google.
Step 3: Create OAuth Credentials
In the APIs & Services section, click Credentials in the left-hand menu.
Click Create Credentials → OAuth Client ID.
Configure the required information:
Application Type
Select the Web Application type.
Application Name
Choose a meaningful name. We recommend using the name of your second-hand site.
This name will be displayed when Google asks users to confirm access.
Authorized JavaScript Origins
Add the URLs where the application will be hosted.
Redirect URI
Add the URI used to receive OAuth responses:
https://secondhand.brand.com/oauth/callback(replace the domain with your site's domain)
Click Create.
Step 4: Retrieve Your Credentials
Once the credentials have been created, retrieve the following information:
Client ID: used to identify the application
Client Secret: used to authenticate the application
These credentials must be shared with the Faume team so that we can complete the integration.
You can also download the JSON file containing this information for future reference.
Step 5: Configure OAuth Permissions
Go to OAuth Consent Screen in the console.
Configure the following information:
Application Name
The name displayed to users when signing in.
Name of your second-hand site.
Application Logo
Add the logo of your second-hand site.
Authorized Domains
Add the domain on which the application will be used:
https://secondhand.brand.comTest Users
Add the users who will be allowed to test the application in development mode.
Click Save and Continue.
This information allows Google to clearly identify your application to your users.
Step 6: Move to Production
Return to the Google Cloud Console.
Publish the application from the OAuth Consent Screen.
Ensure that the redirect URIs and authorized domains are configured correctly.
Before final validation, make sure that all application information has been completed correctly.
Step 7: Share Your Application Information with Faume
Once the configuration is complete:
Share the Client ID with the Faume team
Share the Client Secret with the Faume team
We will then proceed with the final configuration of your site.
Congratulations
Your Google application is now ready to be used with your second-hand site.
Once the credentials have been shared, the Faume team will complete the integration to provide your customers with a simple, fast, and secure login experience.