Injecting Mock JsonWebToken With Qualifiers

[InfoSec812]

According to the documentation here I should be able to do the following:

@InjectMock
@IdToken
JsonWebToken idToken;

But when I try to run my integration tests I get errors like the following:

[1] Unsatisfied dependency for type org.eclipse.microprofile.jwt.JsonWebToken and qualifiers [@IdToken]
        - java member: com.redhat.consultant360.api.AbstractApiController#idToken
        - declared on CLASS bean [types=[com.redhat.consultant360.api.EmployeeApi, com.redhat.consultant360.api.AbstractApiController, com.redhat.consultant360.api.EmployeeApiController, java.lang.Object], qualifiers=[@Default, @Any], target=com.redhat.consultant360.api.EmployeeApiController]

Could someone help me to understand the CORRECT way to inject a mock with qualifiers?

[sberyozkin]

@InfoSec812 Have a look at https://quarkus.io/guides/security-openid-connect#integration-testing-security-annotation

For example, see this test.

[InfoSec812]

Thanks @sberyozkin and that definitely CAN resolve my issue. I am wondering if there might be another option which could be parameterized? Before switching to Quarkus OIDC were were able to inject JsonWebToken using parameterization to test different access restrictions and using per-method annotations will add a lot of work.

[sberyozkin]

@InfoSec812, I see.
@mkouba, hi Martin, is there a way to have a qualifier like @IdToken used with the parameterized mocks ?

[InfoSec812]

Actually, it looks like I should be able to use the WireMock OIDC server to accomplish this, but I am not having much luck so far.

[mkouba]

@InfoSec812, I see. @mkouba, hi Martin, is there a way to have a qualifier like @IdToken used with the parameterized mocks ?

Well, the error message is clear that @IdToken is considered a required qualifier so it should be taken into account. Does the mocked bean also define this qualifier?

[sberyozkin]

@InfoSec812

Actually, it looks like I should be able to use the WireMock OIDC server to accomplish this, but I am not having much luck so far.

Wiremock OIDC server is used to replace a connection to the actual OIDC container, it does not provide any producers for JsonWebToken, for the OIDC specific solution use @TestSecurity alongside @OidcSecurity which is in quarkus-test-security-oidc, as suggested earlier.

Or if I understand Martin's comment correctly, you need to add a quarkus-oidc dependency anyway as the @IdToken is only available in in quarkus-oidc

[InfoSec812]

I think that I will probably post a different question with a different context because using the WireMock OIDC Server is a completely different approach. Thanks for the help!