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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: