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
Copy file name to clipboardExpand all lines: docs/getting-started/gs-normalization-encoding.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ An email hash is a Base64-encoded <Link href="../ref-info/glossary-uid#gl-sha-25
60
60
61
61
The following table shows an example of a simple input email address, and the result as each step is applied to arrive at a secure, opaque value.
62
62
63
-
The final value, the hex to Base64encoded representation of the SHA-256 hash, is the value to provide to the UID2 Operator endpoint.
63
+
The final value, the hex to Base64-encoded representation of the SHA-256 hash, is the value to provide to the UID2 Operator endpoint.
64
64
65
65
:::warning
66
66
When applying Base64 encoding, be sure to Base64-encode the raw bytes of the hash or use a Base64 encoder that takes a hex-encoded value as input. If you use a function that takes text as input, the result is a longer string which is invalid for the purposes of UID2.
@@ -147,7 +147,7 @@ A phone number hash is a Base64-encoded SHA-256 hash of a normalized phone numbe
147
147
148
148
The following table shows an example of a simple input phone number, and the result as each step is applied to arrive at a secure, opaque value.
149
149
150
-
The final value, the hex to Base64encoded representation of the SHA-256 hash, is the value to provide to the UID2 Operator endpoint.
150
+
The final value, the hex to Base64-encoded representation of the SHA-256 hash, is the value to provide to the UID2 Operator endpoint.
151
151
152
152
:::warning
153
153
When applying Base64 encoding, be sure to use a function that takes a hex value as input. If you use a function that takes text as input, the result is a longer string which is invalid for the purposes of UID2.
@@ -162,7 +162,7 @@ When applying Base64 encoding, be sure to use a function that takes a hex value
162
162
163
163
## Example Code
164
164
165
-
For an example of how to generate email and phone hashes in JavaScript, see [Example Code: Hashing and Base-64 Encoding](../guides/integration-javascript-client-side#example-code-hashing-and-base-64-encoding).
165
+
For an example of how to generate email and phone hashes in JavaScript, see [Example Code: Hashing and Base64 Encoding](../guides/integration-javascript-client-side#example-code-hashing-and-base64-encoding).
Copy file name to clipboardExpand all lines: docs/guides/integration-javascript-client-side.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -200,7 +200,7 @@ The following examples demonstrate the different ways that you can configure the
200
200
201
201
If the SDK is configured multiples times, it uses the most recent configuration values.
202
202
203
-
For an example of how to generate email and phone hashes in JavaScript, see [Example Code: Hashing and Base-64 Encoding](#example-code-hashing-and-base-64-encoding).
203
+
For an example of how to generate email and phone hashes in JavaScript, see [Example Code: Hashing and Base64 Encoding](#example-code-hashing-and-base64-encoding).
0 commit comments