@haex-space/vault-sdk 2.5.102 → 2.5.103

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/dist/index.d.mts +8 -9
  2. package/dist/index.d.ts +8 -9
  3. package/package.json +1 -1
package/dist/index.d.mts CHANGED
@@ -91,12 +91,11 @@ declare function installPolyfills(): void;
91
91
  /**
92
92
  * S3-compatible storage configuration provided by the sync server.
93
93
  *
94
- * When using the sync server's S3 proxy, the client authenticates with their
95
- * existing auth token (Bearer token), so accessKeyId and secretAccessKey are
96
- * not needed.
94
+ * The sync server provides per-user S3 credentials that work with any
95
+ * S3-compatible client (AWS CLI, rclone, Cyberduck, rust-s3, etc.).
97
96
  *
98
- * For direct S3 access to providers like AWS S3 or Wasabi, the client would
99
- * provide their own credentials.
97
+ * The server verifies AWS Signature v4 authentication and proxies requests
98
+ * to the underlying storage backend (Supabase Storage).
100
99
  */
101
100
  interface StorageConfig {
102
101
  /** S3 endpoint URL (e.g., "https://sync.haex.space/storage/s3") */
@@ -105,10 +104,10 @@ interface StorageConfig {
105
104
  bucket: string;
106
105
  /** S3 region (usually "auto" for Supabase/proxy) */
107
106
  region: string;
108
- /** Access Key ID - only needed for direct S3 access (AWS, Wasabi, etc.) */
109
- accessKeyId?: string;
110
- /** Secret Access Key - only needed for direct S3 access (AWS, Wasabi, etc.) */
111
- secretAccessKey?: string;
107
+ /** Access Key ID for S3 authentication (format: HAEX + 16 alphanumeric chars) */
108
+ accessKeyId: string;
109
+ /** Secret Access Key for S3 authentication (40 chars, like AWS) */
110
+ secretAccessKey: string;
112
111
  }
113
112
  /**
114
113
  * User info returned from auth endpoints
package/dist/index.d.ts CHANGED
@@ -91,12 +91,11 @@ declare function installPolyfills(): void;
91
91
  /**
92
92
  * S3-compatible storage configuration provided by the sync server.
93
93
  *
94
- * When using the sync server's S3 proxy, the client authenticates with their
95
- * existing auth token (Bearer token), so accessKeyId and secretAccessKey are
96
- * not needed.
94
+ * The sync server provides per-user S3 credentials that work with any
95
+ * S3-compatible client (AWS CLI, rclone, Cyberduck, rust-s3, etc.).
97
96
  *
98
- * For direct S3 access to providers like AWS S3 or Wasabi, the client would
99
- * provide their own credentials.
97
+ * The server verifies AWS Signature v4 authentication and proxies requests
98
+ * to the underlying storage backend (Supabase Storage).
100
99
  */
101
100
  interface StorageConfig {
102
101
  /** S3 endpoint URL (e.g., "https://sync.haex.space/storage/s3") */
@@ -105,10 +104,10 @@ interface StorageConfig {
105
104
  bucket: string;
106
105
  /** S3 region (usually "auto" for Supabase/proxy) */
107
106
  region: string;
108
- /** Access Key ID - only needed for direct S3 access (AWS, Wasabi, etc.) */
109
- accessKeyId?: string;
110
- /** Secret Access Key - only needed for direct S3 access (AWS, Wasabi, etc.) */
111
- secretAccessKey?: string;
107
+ /** Access Key ID for S3 authentication (format: HAEX + 16 alphanumeric chars) */
108
+ accessKeyId: string;
109
+ /** Secret Access Key for S3 authentication (40 chars, like AWS) */
110
+ secretAccessKey: string;
112
111
  }
113
112
  /**
114
113
  * User info returned from auth endpoints
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@haex-space/vault-sdk",
3
- "version": "2.5.102",
3
+ "version": "2.5.103",
4
4
  "description": "SDK for building Haex Vault extensions",
5
5
  "repository": {
6
6
  "type": "git",