Name: Configuring Global Access in SAP Customer Data Cloud
Uploaded: 2024-5-28
Duration: 345 s

Share feedback

<p>Planned maintenance of Practice Systems</p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Subscribe now

Learn more

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div><div><div><div>Global Access gives your customers a consistent user experience on your site, logging into local sites of different data centers as they travel the world. This video will help you understand Global Access in SAP Customer Data Cloud and how it impacts other features like Site Groups, etc.<br><p>Update 2024: Russia is no longer supported as a data center. <br></p><p>Documentation link: <a href="https://help.sap.com/viewer/8b8d6fffe113457094a17701f63e3d6a/GIGYA/en-US/41591cb370b21014bbc5a10ce4041860.html?q=global%20access" rel="nofollow noopener noreferrer" target="_blank">Global Access - SAP Help Portal</a></p></div></div></div></div></div></div></div>

Configuring Global Access in SAP Customer Data Cloud

In this video, we are going  to introduce SAP Customer  Data Cloud's Global  Access, followed by a brief  demo on setting up a site  with global access and the  registration flow. Global  Access allows your  customers to log into their  account on your site,  regardless of their physical  location without having to  create a new account.  That’s because with Global  Access, user data is  created, stored and  retrieved from a single  local data center, even if  the call is made from a  different data center. You  can set the account  residency, or data center  where the user’s data for  your site resides. One of  our 5 data centers can be  set: the US, Europe,  Australia, Russia, or China.  Global Access gives your  customers a consistent  user experience on your  site, logging into local sites  of different data centers as  they travel the world. For  example, if your site is  based in the U.S., a  customer can travel to  Europe and easily login  with the same credentials  to their existing account,  providing them with a  continuous, cohesive  experience with your  brand. User data is stored  in the data center selected  during registration. This  way data residency  regulations are upheld  without compromising  experience. Global Access  applies to site groups as  well. Previously site groups  could exist in only one data  center. Global site groups  transcend this limitation.  Global site groups are site  groups that allow users to  log into all the sites in the  group from different  locations. SAP Customer  Data Cloud replicates the  site configurations in all the  site data centers, including:  site settings, schema,  policies, permission  groups, user keys, and  screen-sets. However, the  user database is never  replicated between data  centers. Thereby, allowing  you to comply with local  data regulations. In  addition, you can provide  global users with a single  sign-on experience. Before  implementing Global Site  Groups, we recommend  that you familiarize yourself  with site groups and how  they work in general.  Before creating your global  site, you should know  which data centers you  wish to include, and which  datacenter to select as  primary. If the site will be  part of a site group, then all  sites in the group must  share the same data  centers and the same  primary data center. For  performance optimization,  the primary datacenter  should be the one that  holds the majority of the  user database, as it will  handle the majority of your  SAP Customer Data Cloud  traffic for your global site or  site group.  In the SAP  Customer Data Cloud  Console, data centers are  shown for each site, with  the primary data center  displayed first and  encircled. Global API keys,  which are also displayed,  are relatively short and  begin with 4_.To register  users in the appropriate  data residency, call the  setAccountResidency API.  This will route the request  to the specified data  center. The data center is  then passed onto the  registration flow via the  screen-sets. When  implementing Global  Access, use  “setAccountResidency” as  part of the registration flow  to determine the data  residency for the  registered user - that is, the  data center where they will  be stored. When global  access is enabled for your  site and a new user  registers, you can view  them on CDC’s Identity  Access page. It now  includes a new data center  column that displays the  relevant flag of the data  center they belong to. The  data center is also  displayed in the user  record. Let’s demo the set  up of a global site. In the  Sites section of the  Console, select Create Site.  In the Add Site window, fill  in the site domain name  and the description…Then  under Data Residency,  select Global Data Center.  In the dropdown, choose  the data centers you wish  to include in the site. Select  the primary location for the  data center. And click OK.   Now you can see the site  and all the data centers it  belongs to with the primary  data center displayed first  and encircled. Global API  keys displayed for sites are  short and start with 4_.  After your global site is  created, continue with site  configurations as you  would for a non-global site.  These steps are explained  in other videos and in our  documentation. Now that  we have created our site  and chosen our data  centers, let’s set up the  Global Access Registration  Flow. The best practice is  to call the  setAccountResidency API  prior to the registration. For  example, you can display  to users the choice of their  residency or nationality,  then call the  setAccountResidency API  to pass their selected  residency. For this demo,  the data residency is set to  China. Next test the global  access registration flow.  Open the website and click  register to bring up the  registration window. Fill out  the form and click submit.  Now let’s go back into the  CDC console and check  the user in Identity Access.  Here you can see the  name and the email of the  user, as well as the data  center storing this user  data. If you go further into  the profile you can also see  the data center for this user  here in the user record as  well. This ends the demo.  Thank you for watching.