@tdxvolt/volt-client-grpc 0.15.0 → 0.16.0-beta.1

package/src/volt-credential.js

@@ -241,12 +241,13 @@ export class VoltCredential {
   }
 
   static rsaEncrypt(key, buffer) {
-    return crypto.publicEncrypt(key, buffer).toString("base64");
+    const cipher = crypto.publicEncrypt(key, buffer);
+    return cipher.toString("base64url");
   }
 
   static rsaDecrypt(key, buffer) {
     const keyObj = crypto.createPrivateKey(key);
-    const cipher = Buffer.from(buffer, "base64");
+    const cipher = Buffer.from(buffer, "base64url");
     return Buffer.from(crypto.privateDecrypt(keyObj, cipher));
   }
 }

package/protobuf/tdx/volt_api/ssi/v1/ssi_api.proto

@@ -1,37 +0,0 @@
-syntax = "proto3";
-
-package tdx.volt_api.ssi.v1;
-
-import "tdx/volt_api/volt/v1/status.proto";
-
-// Volt DIDs are essentially 'peer DIDs', i.e. they are not globally resolvable.
-// TDX DIDs are globally resolvable.
-
-service SsiAPI {
-  rpc ResolveDID(ResolveDIDRequest) returns (ResolveDIDResponse);
-  rpc TrustVerifiableCredential(TrustVerifiableCredentialRequest) returns (TrustVerifiableCredentialResponse);
-}
-
-//
-// Do we need to support/differentiate between plain DIDs and DID urls here?
-// Where a DID url is a DID followed by some additional lookup info,
-// e.g. did:tdx:volt:92181ffa-072a-452a-ae79-a243ab2812fc;service=/some/service?query#fragment
-//
-message ResolveDIDRequest {
-  string did_url = 1;
-}
-
-message ResolveDIDResponse {
-  tdx.volt_api.volt.v1.Status status = 1;
-  string did_document_json = 2;
-}
-
-// Empty ATM - a VC is issued for the authenticated identity.
-message TrustVerifiableCredentialRequest {
-}
-
-message TrustVerifiableCredentialResponse {
-  tdx.volt_api.volt.v1.Status status = 1;
-  string verifiable_credential_json = 2;
-}
-