Sign-in with an Apple ID and a Google account are single sign-on (SSO) authentication methods that allow users to log into apps, websites, or services using their Apple ID or Google account credentials, respectively. These options streamline the login process, enhance security, and reduce the need for managing multiple usernames and passwords.
In order to allow your end-users to log into your vehicle-sharing, rental or ride-hailing mobile apps on the ATOM platform, please follow the below steps to enable these options.
Sign-in with Apple
To enable sign-in with Apple ID into the mobile apps:
Reach out to ATOM support team (help@atommobility.com) and and ask to enable this feature;
ATOM support team will afterwards contact ATOM's backend developer team and the iOS developer and ask them to enable this feature for you;
The developers will perform the necessary changes and upload a new iOS app version for you. Once approved and published, clients will see the sign-in with Apple ID button in your app.
NB! If your users sign in with Apple ID, ATOM will still require users to enter their phone number, but we will skip the OTP verification. That means there is a risk of users entering fake phone numbers.
If your users sign in with Apple ID, they can hide their e-mail address (Apple-specific feature). In these cases, ATOM will list the user's email for example so: xxxxxx@private.email.apple.com
Sign-in with a Google account
In order to enable this option, you will need:
A domain name;
Your Android app, uploaded in Google Play Console;
iOS app must be uploaded in App Store Connect.
To start, you will need to set up your Google APIs console project.
Here's how to do it:
Open your project in the API Console (https://console.cloud.google.com/auth/), or create a project if you don't already have one;
Complete the “Get started” step:
Fill in your app name, add your user support email and click Next:
Choose External:
Add your contact email address:
Agree to the user data policy of Google API Services and click Create:
3. On the branding screen page, make sure all of the information is complete and accurate:
Make sure your app has a correct App Name, App Logo, and App Homepage assigned. These values will be presented to users on the Sign in with Google consent screen on sign up and the Third-party apps & services screen;
Make sure you have specified the URLs of your app's privacy policy and terms of service;
Add authorized domain:
4. Go to the data access page and add 2 scopes (auth/userinfo.email and auth/userinfo.profile):
Click Save:
5. In the Credentials page, create an Android client ID for your app:
You will need to specify your app's package name and SHA-1 signature, you can find this info in Google Play Console (https://play.google.com/console).
Log in and navigate to Test and release > App integrity. Once inside that section, scroll down to "Play app signing" and click on Settings.
Navigate to "App signing key certificate" and copy the value under SHA-1 certificate fingerprint.
Scroll down until you see the final section of the page and the package name:
6. In the Credentials page, create an iOS client ID for your app:
You will need to specify your app's bundle ID, you can find this info in App Store Connect (https://appstoreconnect.apple.com/):
In the Credentials page, create a Web Application client ID for your app:
Publish the app. Go to the Audience page and click the “Publish app” button:
Wait for approval (NB! Skip this step if Google notifies you that verification is not required). Google might send you a follow up email about the verification process. It might include a step that requires an edit in your domain DNS records. After verification is complete the text “In production” will appear under the publishing status:
In the Clients page, copy Android, iOS OAuth and Web application client IDs and send them to the ATOM support team (help@atommobility.com) -
Subject: OAuth client IDs
Message: Android OAuth client ID: xxxx. iOS OAuth client ID: xxxx. Web application client ID: xxxx
That’s it! We’ll notify you once we’ve completed everything on our end.
Google might send you a follow-up email about the verification process. It might include a step that requires an edit in your domain DNS records.
Once all the steps outlined above have been completed, your latest app version will have the sign-in with Apple ID and Google account options visible on the bottom of the sign-in app screen, example below:
Important information:
if a customer uses the regular sign-in process with phone number verification (OTP), his number will be listed as verified in his profile when you check your dashboard;
if a customer signs in with Apple ID or Google account, he will still need to enter his phone number during registration, however it will not be verified via OTP. The number will be listed as unverified in the dashboard:
if a customer uses the regular sign-in process with phone number verification (OTP), but his number was previously used by him or someone else singing in with Apple ID or a Google account, his number will be listed as verified in his current profile when you check your dashboard. The number in the initial profile (with Apple ID or Google account sign-in) where the number was unverified will be changed to +1 000000 followed by a UNIX format timestamp:
