Florian Posch

See https://github.com/eclipse-vertx/vertx-auth/pull/495 (since version 4.2.0) I have the same problem and this broke our attempts to upgrade to vertx4 with keycloak. We don't use specific _audience_ values and so this...

Sorry, any update here? I think @chrispatmore has a point and this definitely broke our existing vertx server when trying to upgrade. We would have to dig into the details...

@vietj Do you also have some input on the initial issue about Access Token audience validation? Is this something you want to fix as suggested by @chrispatmore or will this...

Hi @pmlopes, Sorry for being such a pain. Are there any plans to accept this as an issue and releasing a fix? As I understand it, it is change of...

> In fact on further review of > > ``` > if (target != null && target.size() > 0) { > if (idToken || jwtOptions.getAudience() == null) { > //...

See PR: https://github.com/eclipse-vertx/vertx-auth/pull/673

> Thank you for raising that @fposch, glad the fix works for you, sorry I didn't get to it quicker @chrispatmore Sorry I didn't see _OAuth2Keycloak14IT_ because I was just...

FYI: We didn't want to wait for turnaround from vertx-auth side, so we decided to implement basic audience handling in our application workflows so that we can migrate to vertx4,...

> I can't see any test for this I didn't write a test because I couldn't see any for the provider. A full maven build for the whole vertx-auth module...

Test issues partially fixed, reusing the _audience_ ArrayList from JWTOptions did unintendedly modify its content, using a copy now.