clarify using Base64 value for UID2 #953
Conversation
genwhittTTD
commented
Nov 21, 2025
genwhittTTD
commented
- Multiple mods to normalization doc to clarify re sending Base64
- Refactored email example table
- Added troubleshooting section
| <tr> | ||
| <td>`[email protected]`<br/>`[email protected]`</td> | ||
| <td>1. Normalize<br/>2. Hash<br/>3. Base64-Encode</td> | ||
| <td>`[email protected]`<br/>`16c18d336f0b250f0e2d907452ceb9658a74ecdae8bc94864c23122a72cc27a5`<br/>`FsGNM28LJQ8OLZB0Us65ZYp07NrovJSGTCMSKnLMJ6U=`</td> |
There was a problem hiding this comment.
Processing Steps and Resulting Values are fairly hard to read in its current form - Resulting values are not clearly formatted to correspond to its step clearly as they are in separate cells.
Ideally can we create embedded table within (Processing Steps and Result Values) so that there are cells separation between each step and its value,
or could we just combine (Processing Steps and Result Values) into a single column but we add line of space between each step/value, or colour code each step and its value to make it easier to read?
There was a problem hiding this comment.
@sunnywu Not 100% sure I fully understood what you're suggesting but I added a couple of different treatments as examples (on a subset of the content). LMK if you want one or the other, or a combination, or something else! Thx much.
PS color coding I don't want to go with here... introduces visual inconsistency. That would be a broader conversation.
There was a problem hiding this comment.
Thanks much! Finalized based on #2 -- filled out that table.
|
|
||
| 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. | ||
|
|
||
| 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. |
There was a problem hiding this comment.
Base64 is not URL-safe - the + and / characters have special meaning in URL. There's a separate Base64URL format (replaced with - and _)
There was a problem hiding this comment.
@sunnywu thx much. I just removed this wording -- 2 instances in the doc.
Note that I did not introduce this wording in this PR, it was already there for email and again for phone number. Glad you caught it!
