Skip to content

usnat backwards compatibility for compressed padding#82

Merged
iabmayank merged 1 commit into
IABTechLab:masterfrom
chuff:usnat-backwards-compatibility
Feb 10, 2026
Merged

usnat backwards compatibility for compressed padding#82
iabmayank merged 1 commit into
IABTechLab:masterfrom
chuff:usnat-backwards-compatibility

Conversation

@chuff

@chuff chuff commented Aug 5, 2025

Copy link
Copy Markdown
Contributor

No description provided.

@yuzawa-san

Copy link
Copy Markdown
Contributor

@chuff can you please describe how this broke and why this works in the pr description

@chuff

chuff commented Oct 30, 2025

Copy link
Copy Markdown
Contributor Author

Yeah, basically when DE, IA, NE, NH, NJ, TN was released, USNAT was updated to accommodate 4 additional values for sensitive data processing and 1 additional value for known child sensitive data consents. Since those 2 fields are not at the end of the string, to maintain backwards compatibility, a check needs to be done to see if the string to be parsed was created before or after this change. Since string length is a consistent identifier, I chose that option and injected default values into the string at the correct locations for the newer values.

@yuzawa-san yuzawa-san mentioned this pull request Feb 2, 2026
@iabmayank iabmayank merged commit 230c292 into IABTechLab:master Feb 10, 2026
2 checks passed
chuff added a commit to chuff/iabgpp-java that referenced this pull request Jun 8, 2026
Co-authored-by: Chad Huff <chad@totalium.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants