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

Implement outbound security for gRPC #29

Closed
thegridman opened this issue Mar 20, 2019 · 0 comments
Closed

Implement outbound security for gRPC #29

thegridman opened this issue Mar 20, 2019 · 0 comments
Assignees
Labels
client Client-related issue server Server-related issue

Comments

@thegridman
Copy link
Collaborator

thegridman commented Mar 20, 2019

The web server security examples include examples on how to use outbound security, the same features are required for outbound gRPC calls. Depends on #26 (allow configuration of client security)

The use case is that an authenticated request is made to a Helidon http endpoint and in the code that handles that endpoint another request is made to an external endpoint. This external endpoint requires authentication.

There are two scenarios:

  1. Pass the same credentials through to the external endpoint that were used to access the Helidon endpoint.
  2. Override the credentials by specifying new credentials to use when accessing the external endpoint.

Requirements:

  1. We need to be able to support calling authenticated http endpoints from gRPC methods in the same way as the existing web server examples do.
  2. We need to be able to call authenticated gRPC endpoints from both gRPC methods and web server request handlers using the same patterns as used in the web server examples

Success Criteria:

  1. An authenticated Helidon web service method is able to make an outbound call to an authenticated gRPC service passing through the same credentials that were used to make the web request
  2. An authenticated Helidon web service method is able to make an outbound call to an authenticated gRPC service using different credentials than those were used to make the web request
  3. An non-authenticated Helidon web service method is able to make an outbound call to an authenticated gRPC service using some configured credentials
  4. An authenticated Helidon gRPC service method is able to make an outbound call to an authenticated gRPC service passing through the same credentials that were used to make the web request
  5. An authenticated Helidon gRPC service method is able to make an outbound call to an authenticated gRPC service using different credentials than those were used to make the web request
  6. An non-authenticated Helidon gRPC service method is able to make an outbound call to an authenticated gRPC service using some configured credentials
  7. An authenticated Helidon gRPC service method is able to make an outbound call to an authenticated web service passing through the same credentials that were used to make the web request
  8. An authenticated Helidon gRPC service method is able to make an outbound call to an authenticated web service using different credentials than those were used to make the web request
  9. An non-authenticated Helidon gRPC service method is able to make an outbound call to an authenticated web service using some configured credentials
@thegridman thegridman added server Server-related issue client Client-related issue labels Mar 20, 2019
@thegridman thegridman added this to the Sprint 4/5 milestone Mar 20, 2019
@thegridman thegridman self-assigned this Mar 20, 2019
thegridman added a commit that referenced this issue Mar 26, 2019
Add gRPC outbound security support (issue #29)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client Client-related issue server Server-related issue
Projects
None yet
Development

No branches or pull requests

1 participant