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
So far we have only implemented the PoC for the Attesteer such that it can fetch the Marbles of Marblerun and fetch the enclave quote to send a remote attestation on chain. However, for non-security setups, we need to expose an endpoint to request forwarding of a remote attestation. This should be fairly simple:
Add RPC method to the trusted TLS server to request forwarding. One for IAS and one for DCAP.
We also need to check f the requester has subscribed to using the service. We will probably have a pro-rata billig, so we need a local DB that stores per subscriber: 1. Remaining quota, 2. How many requests have been sent. Not sure about the second though, all the remote attestations are already on the public blockchain.
The text was updated successfully, but these errors were encountered:
So summarizing about what we talked about: The Attesteer shall be used by clients who do not use our SDK; hence we should not use the TrustedOperation in the RPC, which will also remove the double encryption issue for this specific RPC. Steps to do:
Add two commands here: https://github.com/integritee-network/worker/tree/b900e2da99c3d766a2adddd7b2bfb5f46c105f29/cli/src, in a new module attesteer similar to evm and oracle.
Todo: in what format is it the easiest to supply the attestation to the CLI (hex, json)? in a first step, we could also read it from the file system if we have one available/or even hardcode it. -> Go for the quickest solution here, and refine later.
So far we have only implemented the PoC for the Attesteer such that it can fetch the Marbles of Marblerun and fetch the enclave quote to send a remote attestation on chain. However, for non-security setups, we need to expose an endpoint to request forwarding of a remote attestation. This should be fairly simple:
The text was updated successfully, but these errors were encountered: