Skip to content

Commit 90d4091

Browse files
committed
edit
1 parent f8cfffa commit 90d4091

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/getting-started/gs-normalization-encoding.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ For examples of various scenarios, see [Normalization Examples for Email](#norma
5858

5959
An email hash is a Base64-encoded <Link href="../ref-info/glossary-uid#gl-sha-256">SHA-256</Link> hash of a normalized email address. The email address is first normalized, then hashed using the SHA-256 hashing algorithm, and then the resulting bytes of the hash value are encoded using Base64 encoding. Note that the Base64 encoding is applied to the bytes of the hash value, not the hex-encoded string representation.
6060

61-
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, URL-safe value.
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, URL-safe value.
6262

6363
The final value, the hex to Base64 encoded representation of the SHA-256 hash, is the value to provide to the UID2 Operator endpoint.
6464

0 commit comments

Comments
 (0)