Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance authentication #5

Open
sczyh30 opened this issue Oct 30, 2016 · 2 comments
Open

Enhance authentication #5

sczyh30 opened this issue Oct 30, 2016 · 2 comments

Comments

@sczyh30
Copy link
Owner

sczyh30 commented Oct 30, 2016

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.

@a-marcel
Copy link

a-marcel commented Feb 4, 2017

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

@Romeh
Copy link

Romeh commented May 2, 2017

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants