-
Notifications
You must be signed in to change notification settings - Fork 19
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
Attestation APIs #63
Attestation APIs #63
Conversation
text/0063-attestation-grpc-apis.md
Outdated
Teaclave uses gRPC with a generic payload that is deserialized as JSON, | ||
<https://teaclave.apache.org/docs/codebase/rpc/>. This limits to one message | ||
type, which means it limits to clients only needing to know about one service. | ||
Clients need to deserialize and redirect the message to the correct recipient. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is what we do after attestation. We use a common service for all other requests. Is there good reason to keep attest as a separate service? maybe that should go in the questions section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In practice, we will not actually have a separate attest
service, because the load balancers can't deal with that.
Co-authored-by: Chris Beck <5683852+cbeck88@users.noreply.github.com>
Closing this for now |
Rendered MCIP