jHipster-Quarkus microservice creates code/logic around user authentication

[rajesh-ryse]

Overview of the feature request

Every time a new Quarkus microservice is created using jHipster-Quarkus, a bunch of code related to user authentication including jwt token management is create.
This is not necessary as the authentication is mostly centralized with token being propagated to different microservices.

The authentication code should be allowed as an option for the user to select.

Motivation for or Use Case

Every time a microservice is created, time is spent in code cleanup.

• [x ] Checking this box is mandatory (this is just to show you read everything)

[emilpaw]

This is an issue for JHipster Quarkus, not the main generator.

[mshima]

@rajesh-ryse you should list files you think it should be removed, a PR is welcome.
I cannot transfer the issue to quarkus blueprint.

[DanielFran]

@rajesh-ryse @mshima transfered to quarkus blueprint project