Implementing the Phone Number Login Authentication Option

Objective

After completing this lesson, you will be able to manage the Phone Number Login authentication option to offer customers greater flexibility when logging into an account.

Phone Number Authentication

In areas where email usage is less prevalent, users are more reliant on mobile phones. Implementing a phone number login option provides these users with a seamless, convenient, and secure authentication experience.

Hand holding a phone with a dialing keypad displayed on the front. Three icons below it indicate Member ID, Email, and Social. A text box says: Phone ID can serve as a full authentication option for customers where email is less prevalent. Advantages of using one-time password and phone verification are: Greater support where cell phone has mass adoption, an array of authentication options, and a greater flexibility to onboard new customers.

Phone Number login offers passwordless authentication using a one-time SMS code. The registration and login flows are identical. If the user's phone doesn't exist in your database, a new account is created (user registration). if the phone exists, the user logs in to their existing account.

Benefits of Phone Number Login

  • Enhanced Security – Secures digital property logins with one-time password and phone number verification.
  • Expanded Reach – Greater support for customers in regions where email is less prevalent and cell phones have mass adoption.
  • Versatile Authentication – Complements existing authentication options like email, username, federated access, and social network logins.
  • Simplified Onboarding – Offers great flexibility to onboard new customers using their preferred authentication method.
Four images illustrating Configure SMS providers to sent OTP/OTC, Phone number allow list and deny list, pre-built screen-set for Phone ID authentication, and Login with a combination of phone ID and OTP/OTC.

For more information refer to the Phone Number Logindocumentation in the SAP Help Portal.

Implementing Phone Number Login in SAP Customer Data Cloud

Three-screen sequence showing the customer selecting their country code before entering their phone number, leading to a dialog box where they're invited to enter the code sent to their phone.

The mobile login screens are included in the RegistrationLogin screen-set. It is important to only use the Mobile Login screens for phone number login, as other screens may not fully support this functionality.

To implement the Phone Number Login, follow these steps:

  1. Open the SAP Customer Data Cloud console and go to the Screen-Sets page.
  2. The mobile login screens are included in the RegistrationLogin screen-set. Open that screen-set to edit them.
  3. Select the Mobile Login or the Mobile Login Verification screens on the left-hand menu under Screens.
  4. Customize the Screen: You may change colors, assign CSS, and modify the look and feel of the screen, but avoid adding input fields.
  5. Save your changes.

For more information on editing screens, check the UI Builder options in the SAP Help Portal.

Consent and Compliance

Ensure that all necessary consent statements are included on the Registration Completion screen to gather consent from a user registering with a phone number login (assuming you are using SAP Enterprise Consent and Preference Management).

If your site policy includes COPPA compliance, include the birth date fields in the Registration Completion screen.

SMS Providers

Screenshot of SMS Providers page, listing as supported providers: LiveLink, Twilio, Sinch, and Karaden. Levels of configuration are Partner and Site.

SAP Customer Data Cloud requires an external SMS service provider to send SMS texts to end users.

SAP Customer Data Cloud currently supports the following providers:

  • LiveLink
  • Twilio
  • Sinch
  • Karaden

You can also use a different SMS provider or apply advanced options and custom logic by using Extensions.

When you configure SMS providers at the partner level (inside the Administration section of the console), this configuration is inherited and applied to every site within that partner. If you need a different configuration for specific sites, you can further refine your configured SMS providers using a different configuration at the site or site group level.

To use Site-Level SMS Provider configuration, you must first enable SMS for your partner by configuring it at the Partner level inside the Administration section of the console.

For more information refer to the SMS Providersdocumentation in the SAP Help Portal.

Summary

  • Phone Number Login enhances user experience by offering passwordless authentication via SMS codes.
  • Implementing Phone Number Login involves configuring screen-sets, managing consent, and integrating with REST APIs.
  • SAP Customer Data Cloud supports various SMS providers, allowing for flexible configuration at partner and site levels.
Learning
SAP FacebookSAP YoutubeSAP LinkedIn