vertx-blueprint-microservice icon indicating copy to clipboard operation
vertx-blueprint-microservice copied to clipboard

Published 20 hours ago • verified publisher icon sczyh30

Enhance authentication

Open sczyh30 opened this issue 7 years ago • 2 comments

Current authentication implementation in the API Gateway is not very concise, and only supports Keycloak via Vert.x OAuth 2. So it's necessary to enhance the implementation of authentication. Maybe an individual authentication component is needed.

sczyh30 avatar Oct 30 '16 13:10 sczyh30

Hi,

if you change the auth maybe you can consider that it could be possible that a microservice is reachable without the API Gateway.

For decoupling the services and prevent problems with the api gateway (single point of failure), it could be possible that the clients goes directly to some microservices with the same token/session id.

From my point of view the usage of vertx JWT is a good idea too.

Thanks Marcel

a-marcel avatar Feb 04 '17 17:02 a-marcel

yes JWT would be a better choice if you go with clean clean micro services design for service to service API trust

Romeh avatar May 02 '17 08:05 Romeh