Skip to content

Conversation

@aulme
Copy link
Contributor

@aulme aulme commented Jun 4, 2025

No description provided.

@aulme aulme force-pushed the aul-UID2-4666-batch-e2e-for-identity-map branch from c96e802 to 7fff38b Compare June 4, 2025 09:46
assertThat(response.at("/status").asText()).isEqualTo("success");
}

@ParameterizedTest(name = "/v2/identity/map - {0} - {2}")

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to be clear, did we only want to test v2 identity map here and not v3?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We want both, but we don't have Identity Map V3 SDK yet. It's not merged, and the tests go via the SDK. I'll add the v3 test when we have the SDK merged.

private static String randomHash() {
// This isn't really a hashed DII but looks like one ot UID2
byte[] randomBytes = new byte[32];
RANDOM.nextBytes(randomBytes);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would this result in an invalid mapping or would it return some UID2 in the response?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be some UID2. We don't check, and cannot possibly check, whether the hash maps back to any valid DII. From our perspective, it's just a certain amount of bytes.

@aulme aulme merged commit e6c5a70 into main Jun 6, 2025
4 checks passed
@aulme aulme deleted the aul-UID2-4666-batch-e2e-for-identity-map branch June 6, 2025 00:43
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.

3 participants