LiveRamp Embedded Identity in Databricks
LiveRamp's Embedded Identity is available in Databricks through a Delta Share. A Delta Share is a read-only version of the data that allows LiveRamp access to the customer data for resolution and allows LiveRamp to share back the resolved data. More information on Delta Sharing can be found here.
There is currently one available operation that you can perform using Embedded Identity in Databricks:
RampID Identity Resolution: This solution allows you to resolve an identifier (PII, such as name, address, email, or phone) to LiveRamp's person-based, pseudonymous identifier, RampID. For more information, see "Perform RampID Identity Resolution in Databricks".
Note
This workflow is in limited availability and is by invitation only.
Enabling LiveRamp Embedded Identity in Databricks
To enable LiveRamp Embedded Identity in Databricks, the following tasks must be performed:
You execute an agreement with LiveRamp to access the service.
LiveRamp reviews the use case, including any additional Data Ethics reviews if required.
If you don’t already have credentials for LiveRamp's Identity API, LiveRamp sends you a client ID and a secret for authentication.
Authentication
The LiveRamp Identity Service in Databricks relies on the same authentication service as LiveRamp's AbiliTec and RampID APIs (Identity APIs). If you have credentials for those APIs, you can use your previously assigned credentials.
Authenticating with LiveRamp's Embedded Identity service requires a call to LiveRamp's core services within the process.
Client credentials are used to obtain an access token by passing the client ID and client secret values. For information, see "About Identity Authentication."