You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This article explains the concept of Face liveness quick link, its usage flow, and related concepts.
20
19
21
20
## Introduction
22
21
23
-
Azure Liveness Quick Link is an optional integration path for [Face liveness detection](concept-face-liveness-detection.md). It exchanges a liveness session’s session-authorization-token for a singleuse URL that hosts the capture experience on an Azureoperated page. The service returns to a developersupplied callback endpoint after finishing the operation.
22
+
Azure Face Liveness quick link is an optional integration path for [Face liveness detection](concept-face-liveness-detection.md). It exchanges a liveness session’s session-authorization-token for a single-use URL that hosts the face capture experience on an Azure-operated page. The service returns to a developer-supplied callback endpoint after finishing the operation.
24
23
25
-
Azure Liveness Quick Link provides multiple benefits to customers:
26
-
-No need to embed the liveness client SDK. Easier integration in application side.
27
-
-No need to keep track of liveness client SDK updates. Azureoperated websites always use the latest and greatest version of liveness detection.
24
+
Azure Liveness quick link provides multiple benefits to customers:
25
+
-You don't need to embed the liveness client SDK. That allows for easier integration on the application side.
26
+
-You don't need to keep track of liveness client SDK updates. Azure-operated websites always use the latest version of liveness detection.
28
27
29
28
## How it works
30
29
31
-
You can utilize the liveness quick link websiteliveness.face.azure.com to turn a liveness session into a shareable, single use link:
30
+
You can use the liveness quick link website, `liveness.face.azure.com`, to turn a liveness session into a shareable, single use link:
32
31
33
32
:::image type="content" source="media/liveness/liveness-quick-link-diagram.png" alt-text="A diagram illustrates liveness quick link work flow":::
34
33
35
-
1. Start a session server side. Your backend asks Face API for a new liveness session and receives a shortlived authorization token that represents that session.
36
-
2. Swap the token for a link. Your backend sends the token to the Quick Link service, which creates a onetime URL tied to the session. here are examples to post request:
34
+
1. Start a session with your server-side code. Your application backend requests a new liveness session from the Face API and receives a short-lived authorization token that represents that session.
35
+
2. Swap the session token for a link. Your application backend sends the token to the quick link service, which creates a one-time URL connected to the session. Here are examples of the post request:
37
36
38
37
#### [C#](#tab/csharp)
39
38
```csharp
@@ -113,16 +112,20 @@ You can utilize the liveness quick link website liveness.face.azure.com to turn
Compose the returned url after liveness quick link web site `https://liveness.face.azure.com/?s=60c3980c-d9f6-4b16-a7f5-f1f4ad2b506f`
125
-
126
-
3. Send the link to the user. You can redirect the browser, show a button, or display a QR code—anything that gets the user to open the link on a camera enabled device.
127
-
4. Azure hosts the capture. When the link opens, the Azure operated page guides the user through the liveness check sequence using the latest Liveness Web Client.
128
-
5. Get the outcome callback. As soon as the check finishes—or if the user abandons or times out—Quick Link notify to your callback endpoint so your application can decide what happens next.
115
+
```
116
+
117
+
---
118
+
119
+
The following is an example response:
120
+
121
+
```json
122
+
{
123
+
"url": "/?s=60c3980c-d9f6-4b16-a7f5-f1f4ad2b506f"
124
+
}
125
+
```
126
+
127
+
Use that value to construct the liveness quick link web page: `https://liveness.face.azure.com/?s=60c3980c-d9f6-4b16-a7f5-f1f4ad2b506f`
128
+
129
+
1. Send the link to the user. You can redirect the browser, show a button, or display a QR code—anything that lets the user open the link on a camera-enabled device.
130
+
1. Azure hosts the capture experience. When the link opens, the Azure-operated page guides the user through the liveness check sequence using the latest Liveness web client.
131
+
1. Get the outcome callback. As soon as the check finishes—or if the user abandons or times out—the quick link service notifies your callback endpoint so your application can decide what happens next.
0 commit comments