[data-plane]: TokenVerifier: execute blocking calls in parallel (ordered = false)

[creydr]

Currently we don't disable the ordering of the blocking call in

eventing-kafka-broker/data-plane/core/src/main/java/dev/knative/eventing/kafka/broker/core/oidc/TokenVerifier.java

Lines 43 to 59 in 02be94e

	return this.vertx.<JwtClaims>executeBlocking(promise -> {
	// execute blocking, as jose .process() is blocking
	JwtConsumer jwtConsumer = new JwtConsumerBuilder()
	.setVerificationKeyResolver(this.oidcDiscoveryConfig.getJwksVerificationKeyResolver())
	.setExpectedAudience(expectedAudience)
	.setExpectedIssuer(this.oidcDiscoveryConfig.getIssuer())
	.build();
	try {
	JwtContext jwtContext = jwtConsumer.process(token);
	promise.complete(jwtContext.getJwtClaims());
	} catch (InvalidJwtException e) {
	promise.fail(e);
	}
	});

.
This leads to non-parallel/serial calls and thus reduced throughput.

...
ordered – if true then if executeBlocking is called several times on the same context, the executions for that context will be executed serially, not in parallel. if false then they will be no ordering guarantees

Therefor we should check if we can use vertx.executeBlocking(handler, ordered) with ordered = false.

Additional Information:

• TokenVerifier class (attention: might be renamed to TokenVerifierImpl in Receiver reject requests for wrong audience #3675)
• executeBlocking java doc

[pierDipi]

@creydr do you think this could be a good first issue ?

[pierDipi]

/triage accepted

[creydr]

@creydr do you think this could be a good first issue ?

I think so. I added some more information in the description.

/kind good-first-issue

[parth721]

Hi @creydr I would love to work on this good first issue.

[parth721]

/assign