Social logins allow a customer to login using either their Google or Facebook accounts without having to create another set of credential just to login to LatePoint.
When the user is presented with the login option an additional button for Google is placed at the bottom of any login window.
Using this button clients can use their social credentials to pre-fil in the customer information that is already entered in the social accounts.
Configuring Google
Login to google developers at https://developers.google.com/identity/sign-in/web/sign-in
- Go to the Credentials page.
- View and edit an existing application or
- Create an new project.
- The New Project dialogue will open where you can assign a meaningful Project Name. In this case we have called it LatePoint.
- After you have put in a project name press create.
- The project credentials screen will now open with the ability to create credentials for the project.
6. Select the Create Credentials, select OAuth client ID and start the wizard.
7. Configure Consent Screen
8. The Consent Screen allows for some visual identity type verifications so the client can see they are in fact logging into your site. There are 4 steps to work through.
Step 1 OAuth consent you need:
- App Name
- Support Email
- App Logo (120px x 120px)
- App Domain information
- Application Home Page
- Privacy Policy
- Terms of Service
- Authorized domains
- Developer contact information
Step 2 Scopes
You can save and continue this step with no information selected.
(When using the google calendar a scope is required)
Step 3 Test users
You can setup test google users to check login verifications once the login app is live.
Step 4 Summary
Review the information and select “Back to the dashboard”
From here the App is ready to be published
You can choose the two different types of status for your App
In Production:
Once you set your app status as “In production,” your app will be available to anyone with a Google Account. Depending on how you configure your OAuth screen, you may have to submit your app for verification .
Testing:
If your app is still being tested and built, you can set your status to “testing”. In this state, you can test your app with a limited number of users.
After configuration is complete, take note of the client ID that was created. You will need the client ID to complete the next steps. (A client secret is also created, but you need it only for server-side operations.)
From here you can Publish your app
Because you have published a new app the status needs to be verified.
Enter any verification details that may be required and submit for verification.
Credentials now need to be created so that the application can link the submission with certain web site addresses.
Create OAuth client ID
Select the Application type as Web application and provide a name
Authorised JavaScrip origins and redirect URIs
The JavaScript origin is you main website address
The Authorized redirect URIs will be any pages that require a login type prompt.
LatePoint pages will need to be included in the redirect URIs and are shown in the settings>settings>general screen under Setup Pages
Configuring Google Settings in LatePoint
Once you select Create your Client ID and Secret are shown. Keep this window open to allow you to copy and paste the credentials into the LatePoint configuration window.
Under settings>settings>general>social login check the “Enable Login with Google” and paste the google credentials just created.
Ensure you click save at the bottom of the settings window.
Now when you users either book a session or login to their accounts they will be presented with a google login option.
