Hi Anand! There are a lot of ways to test quarkus applications (including/mocking auth).

You can always get a "real" token for a real user with restassured, but i highly recommend not to do that, at least not against external auth server resources.

This might look something like this (simple oauth2):

  public static String getToken() {
    return RestAssured
        .given()
        .param("grant_type", "password")
        .param("username", "admin")
        .param("password", "changeme")
        .param("client_id", "your-client-id")
        .when()
        .post(KEYCLOAK_SERVER_URL + "/realms/master/protocol/openid-connect/token")
        .as(AccessTokenResponse.class).getToken(); // class from keycloak library
  }

You should at least have some kind of dev keycloak running for your tests (https://quarkus.io/guides/dev-services#keycloak). This can be done manually or using one of built in quarkus features. I recommend reading up https://quarkus.io/guides/security-keycloak-authorization#testing-the-application.

The better way to test your rest application is to mock authorization (with any kind of user you have). This looks something like this:

  @QuarkusTest 
	
	// ....


    @TestSecurity(user = "anyservice", roles = {"public-holidays.read"})
    @Test
    public void testGetDateWrongFormat() {
        given()
                .when().get("/day/2021")
                .then()
                .statusCode(400);
    }

You can "fake" all your token information without having the need for any auth server process.

Btw you should do the same with your database: Having a "Mock" Database makes running CI Tests way easier and you can turn on continous testing in quarkus: https://quarkus.io/guides/continuous-testing.