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

HTTP Bindings #14

Open
cyberphone opened this issue Mar 29, 2019 · 0 comments
Open

HTTP Bindings #14

cyberphone opened this issue Mar 29, 2019 · 0 comments

Comments

@cyberphone
Copy link

It seems that cloud based TEEs and client based TEEs would work differently (protocol wise) during provisioning, at least when HTTP is used as transport.

Client based TEE:
Request is coming from the client side (outbound) which means that the TAM request data must be delivered in a HTTP response body while the TEE response is delivered in a subsequent HTTP POST request.

Cloud based TEE:
Request is coming from an outside service in the from of an HTTP POST request while the TEE response is returned in the associated HTTP response body.

Another difference is that in a cloud based scenario, the requester (TAM) must also be authenticated as a legitimate cloud service account user. This is a part of an HTTP binding scheme as well.

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

No branches or pull requests

1 participant