You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Pass the same credentials through to the external endpoint that were used to access the Helidon endpoint.
Override the credentials by specifying new credentials to use when accessing the external endpoint.
Requirements:
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.
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:
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
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
An non-authenticated Helidon web service method is able to make an outbound call to an authenticated gRPC service using some configured credentials
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
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
An non-authenticated Helidon gRPC service method is able to make an outbound call to an authenticated gRPC service using some configured credentials
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
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
An non-authenticated Helidon gRPC service method is able to make an outbound call to an authenticated web service using some configured credentials
The text was updated successfully, but these errors were encountered:
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:
Requirements:
Success Criteria:
The text was updated successfully, but these errors were encountered: