@meeco/svx-api-sdk 1.0.0-stage.20240502114933.d123429 → 1.0.0-stage.20240703124311.f085df0

package/lib/umd/apis/SecurityRightsApi.js

@@ -5,7 +5,7 @@
  * SVX API
  * No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
  *
- * The version of the OpenAPI document: 1.3.5
+ * The version of the OpenAPI document: 1.3.6
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -52,86 +52,6 @@ const models_1 = require("../models");
  *
  */
 class SecurityRightsApi extends runtime.BaseAPI {
-    /**
-     *   Assign global security rights to a user.    The user we are assigning security rights to does not need to be known by ATOM.    In order to execute this action the current user must have security right `atom:global:assign_global_sr_to_user`.
-     * Assign global security rights to a user
-     */
-    globalAdminsAdminIdSecurityRightsPostRaw(requestParameters, initOverrides) {
-        return __awaiter(this, void 0, void 0, function* () {
-            if (requestParameters.adminId === null || requestParameters.adminId === undefined) {
-                throw new runtime.RequiredError('adminId', 'Required parameter requestParameters.adminId was null or undefined when calling globalAdminsAdminIdSecurityRightsPost.');
-            }
-            if (requestParameters.aTOMAssignSecurityRightsRequest === null || requestParameters.aTOMAssignSecurityRightsRequest === undefined) {
-                throw new runtime.RequiredError('aTOMAssignSecurityRightsRequest', 'Required parameter requestParameters.aTOMAssignSecurityRightsRequest was null or undefined when calling globalAdminsAdminIdSecurityRightsPost.');
-            }
-            const queryParameters = {};
-            const headerParameters = {};
-            headerParameters['Content-Type'] = 'application/json';
-            if (this.configuration && this.configuration.accessToken) {
-                const token = this.configuration.accessToken;
-                const tokenString = yield token("SVX-JWT", []);
-                if (tokenString) {
-                    headerParameters["Authorization"] = `Bearer ${tokenString}`;
-                }
-            }
-            const response = yield this.request({
-                path: `/global_admins/{admin_id}/security_rights`.replace(`{${"admin_id"}}`, encodeURIComponent(String(requestParameters.adminId))),
-                method: 'POST',
-                headers: headerParameters,
-                query: queryParameters,
-                body: (0, models_1.ATOMAssignSecurityRightsRequestToJSON)(requestParameters.aTOMAssignSecurityRightsRequest),
-            }, initOverrides);
-            return new runtime.VoidApiResponse(response);
-        });
-    }
-    /**
-     *   Assign global security rights to a user.    The user we are assigning security rights to does not need to be known by ATOM.    In order to execute this action the current user must have security right `atom:global:assign_global_sr_to_user`.
-     * Assign global security rights to a user
-     */
-    globalAdminsAdminIdSecurityRightsPost(adminId, aTOMAssignSecurityRightsRequest, initOverrides) {
-        return __awaiter(this, void 0, void 0, function* () {
-            yield this.globalAdminsAdminIdSecurityRightsPostRaw({ adminId: adminId, aTOMAssignSecurityRightsRequest: aTOMAssignSecurityRightsRequest }, initOverrides);
-        });
-    }
-    /**
-     *   Remove global security rights from a user.    In order to execute this action the current user must have security right `atom:global:assign_global_sr_to_user`.
-     * Remove global security rights from a user
-     */
-    globalAdminsAdminIdSecurityRightsSecurityRightsDeleteRaw(requestParameters, initOverrides) {
-        return __awaiter(this, void 0, void 0, function* () {
-            if (requestParameters.adminId === null || requestParameters.adminId === undefined) {
-                throw new runtime.RequiredError('adminId', 'Required parameter requestParameters.adminId was null or undefined when calling globalAdminsAdminIdSecurityRightsSecurityRightsDelete.');
-            }
-            if (requestParameters.securityRights === null || requestParameters.securityRights === undefined) {
-                throw new runtime.RequiredError('securityRights', 'Required parameter requestParameters.securityRights was null or undefined when calling globalAdminsAdminIdSecurityRightsSecurityRightsDelete.');
-            }
-            const queryParameters = {};
-            const headerParameters = {};
-            if (this.configuration && this.configuration.accessToken) {
-                const token = this.configuration.accessToken;
-                const tokenString = yield token("SVX-JWT", []);
-                if (tokenString) {
-                    headerParameters["Authorization"] = `Bearer ${tokenString}`;
-                }
-            }
-            const response = yield this.request({
-                path: `/global_admins/{admin_id}/security_rights/{security_rights}`.replace(`{${"admin_id"}}`, encodeURIComponent(String(requestParameters.adminId))).replace(`{${"security_rights"}}`, encodeURIComponent(String(requestParameters.securityRights))),
-                method: 'DELETE',
-                headers: headerParameters,
-                query: queryParameters,
-            }, initOverrides);
-            return new runtime.VoidApiResponse(response);
-        });
-    }
-    /**
-     *   Remove global security rights from a user.    In order to execute this action the current user must have security right `atom:global:assign_global_sr_to_user`.
-     * Remove global security rights from a user
-     */
-    globalAdminsAdminIdSecurityRightsSecurityRightsDelete(adminId, securityRights, initOverrides) {
-        return __awaiter(this, void 0, void 0, function* () {
-            yield this.globalAdminsAdminIdSecurityRightsSecurityRightsDeleteRaw({ adminId: adminId, securityRights: securityRights }, initOverrides);
-        });
-    }
     /**
      *   List all users with global security rights.    It is also possible to request a list of archived global admins, that is, users who used to have global security rights, but do not have them now.    In order to execute this action the current user must have \"security right `atom:global:assign_global_sr_to_user`.
      * List all users with global security rights
@@ -330,6 +250,86 @@ class SecurityRightsApi extends runtime.BaseAPI {
             return yield response.value();
         });
     }
+    /**
+     *   Assign global security rights to a user.    The user we are assigning security rights to does not need to be known by ATOM.    In order to execute this action the current user must have security right `atom:global:assign_global_sr_to_user`.
+     * Assign global security rights to a user
+     */
+    globalAdminsIdSecurityRightsPostRaw(requestParameters, initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            if (requestParameters.id === null || requestParameters.id === undefined) {
+                throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling globalAdminsIdSecurityRightsPost.');
+            }
+            if (requestParameters.aTOMAssignSecurityRightsRequest === null || requestParameters.aTOMAssignSecurityRightsRequest === undefined) {
+                throw new runtime.RequiredError('aTOMAssignSecurityRightsRequest', 'Required parameter requestParameters.aTOMAssignSecurityRightsRequest was null or undefined when calling globalAdminsIdSecurityRightsPost.');
+            }
+            const queryParameters = {};
+            const headerParameters = {};
+            headerParameters['Content-Type'] = 'application/json';
+            if (this.configuration && this.configuration.accessToken) {
+                const token = this.configuration.accessToken;
+                const tokenString = yield token("SVX-JWT", []);
+                if (tokenString) {
+                    headerParameters["Authorization"] = `Bearer ${tokenString}`;
+                }
+            }
+            const response = yield this.request({
+                path: `/global_admins/{id}/security_rights`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))),
+                method: 'POST',
+                headers: headerParameters,
+                query: queryParameters,
+                body: (0, models_1.ATOMAssignSecurityRightsRequestToJSON)(requestParameters.aTOMAssignSecurityRightsRequest),
+            }, initOverrides);
+            return new runtime.VoidApiResponse(response);
+        });
+    }
+    /**
+     *   Assign global security rights to a user.    The user we are assigning security rights to does not need to be known by ATOM.    In order to execute this action the current user must have security right `atom:global:assign_global_sr_to_user`.
+     * Assign global security rights to a user
+     */
+    globalAdminsIdSecurityRightsPost(id, aTOMAssignSecurityRightsRequest, initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            yield this.globalAdminsIdSecurityRightsPostRaw({ id: id, aTOMAssignSecurityRightsRequest: aTOMAssignSecurityRightsRequest }, initOverrides);
+        });
+    }
+    /**
+     *   Remove global security rights from a user.    In order to execute this action the current user must have security right `atom:global:assign_global_sr_to_user`.
+     * Remove global security rights from a user
+     */
+    globalAdminsIdSecurityRightsSecurityRightsDeleteRaw(requestParameters, initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            if (requestParameters.id === null || requestParameters.id === undefined) {
+                throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling globalAdminsIdSecurityRightsSecurityRightsDelete.');
+            }
+            if (requestParameters.securityRights === null || requestParameters.securityRights === undefined) {
+                throw new runtime.RequiredError('securityRights', 'Required parameter requestParameters.securityRights was null or undefined when calling globalAdminsIdSecurityRightsSecurityRightsDelete.');
+            }
+            const queryParameters = {};
+            const headerParameters = {};
+            if (this.configuration && this.configuration.accessToken) {
+                const token = this.configuration.accessToken;
+                const tokenString = yield token("SVX-JWT", []);
+                if (tokenString) {
+                    headerParameters["Authorization"] = `Bearer ${tokenString}`;
+                }
+            }
+            const response = yield this.request({
+                path: `/global_admins/{id}/security_rights/{security_rights}`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))).replace(`{${"security_rights"}}`, encodeURIComponent(String(requestParameters.securityRights))),
+                method: 'DELETE',
+                headers: headerParameters,
+                query: queryParameters,
+            }, initOverrides);
+            return new runtime.VoidApiResponse(response);
+        });
+    }
+    /**
+     *   Remove global security rights from a user.    In order to execute this action the current user must have security right `atom:global:assign_global_sr_to_user`.
+     * Remove global security rights from a user
+     */
+    globalAdminsIdSecurityRightsSecurityRightsDelete(id, securityRights, initOverrides) {
+        return __awaiter(this, void 0, void 0, function* () {
+            yield this.globalAdminsIdSecurityRightsSecurityRightsDeleteRaw({ id: id, securityRights: securityRights }, initOverrides);
+        });
+    }
     /**
      * Show all security rights of the current user for all active tenants and organizations
      * All security rights of the current user

package/lib/umd/apis/SharesApi.js

@@ -5,7 +5,7 @@
  * SVX API
  * No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
  *
- * The version of the OpenAPI document: 1.3.5
+ * The version of the OpenAPI document: 1.3.6
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -288,10 +288,10 @@ class SharesApi extends runtime.BaseAPI {
      * Re-encrypt share data  Data in shared slots is initially encrypted with the share DEK. The share DEK is encrypted with the public key of the share recipient. When processing a share the client application is expected to decrypt the slot data as well as `encrypted_value_verification_key` and re-encrypt with them private DEK with this endpoint.
      * Re-encrypt share data
      */
-    itemsIdEncryptPostRaw(requestParameters, initOverrides) {
+    itemsItemIdEncryptPostRaw(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            if (requestParameters.id === null || requestParameters.id === undefined) {
-                throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling itemsIdEncryptPost.');
+            if (requestParameters.itemId === null || requestParameters.itemId === undefined) {
+                throw new runtime.RequiredError('itemId', 'Required parameter requestParameters.itemId was null or undefined when calling itemsItemIdEncryptPost.');
             }
             const queryParameters = {};
             const headerParameters = {};
@@ -310,7 +310,7 @@ class SharesApi extends runtime.BaseAPI {
                 }
             }
             const response = yield this.request({
-                path: `/items/{id}/encrypt`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))),
+                path: `/items/{item_id}/encrypt`.replace(`{${"item_id"}}`, encodeURIComponent(String(requestParameters.itemId))),
                 method: 'POST',
                 headers: headerParameters,
                 query: queryParameters,
@@ -323,9 +323,9 @@ class SharesApi extends runtime.BaseAPI {
      * Re-encrypt share data  Data in shared slots is initially encrypted with the share DEK. The share DEK is encrypted with the public key of the share recipient. When processing a share the client application is expected to decrypt the slot data as well as `encrypted_value_verification_key` and re-encrypt with them private DEK with this endpoint.
      * Re-encrypt share data
      */
-    itemsIdEncryptPost(id, meecoDelegationId, meecoOrganisationId, postItemEncryptRequest, initOverrides) {
+    itemsItemIdEncryptPost(itemId, meecoDelegationId, meecoOrganisationId, postItemEncryptRequest, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.itemsIdEncryptPostRaw({ id: id, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, postItemEncryptRequest: postItemEncryptRequest }, initOverrides);
+            const response = yield this.itemsItemIdEncryptPostRaw({ itemId: itemId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, postItemEncryptRequest: postItemEncryptRequest }, initOverrides);
             return yield response.value();
         });
     }
@@ -333,10 +333,10 @@ class SharesApi extends runtime.BaseAPI {
      * Updating all shares of one item is done by the item owner in one go.   A share DEK is encrypted with a public key of the recipient. In order to update shares the owner needs a public key of the recipient of each share. But some shares may be created by users different from the owner, and thus the owner might have no connection to recipients of those shares, and no access to those shares.  This problem is solved by * Putting a public key of the recipient and an identification of the keypair to which the public key belongs into each share record. * Providing a list of all public keys and share IDs for all shares of the given item via this endpoint   Getting this list is the first step in updating all shares of the item.
      * Prepare an update of all shares of one item
      */
-    itemsIdSharesGetRaw(requestParameters, initOverrides) {
+    itemsItemIdSharesGetRaw(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            if (requestParameters.id === null || requestParameters.id === undefined) {
-                throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling itemsIdSharesGet.');
+            if (requestParameters.itemId === null || requestParameters.itemId === undefined) {
+                throw new runtime.RequiredError('itemId', 'Required parameter requestParameters.itemId was null or undefined when calling itemsItemIdSharesGet.');
             }
             const queryParameters = {};
             const headerParameters = {};
@@ -354,7 +354,7 @@ class SharesApi extends runtime.BaseAPI {
                 }
             }
             const response = yield this.request({
-                path: `/items/{id}/shares`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))),
+                path: `/items/{item_id}/shares`.replace(`{${"item_id"}}`, encodeURIComponent(String(requestParameters.itemId))),
                 method: 'GET',
                 headers: headerParameters,
                 query: queryParameters,
@@ -366,9 +366,9 @@ class SharesApi extends runtime.BaseAPI {
      * Updating all shares of one item is done by the item owner in one go.   A share DEK is encrypted with a public key of the recipient. In order to update shares the owner needs a public key of the recipient of each share. But some shares may be created by users different from the owner, and thus the owner might have no connection to recipients of those shares, and no access to those shares.  This problem is solved by * Putting a public key of the recipient and an identification of the keypair to which the public key belongs into each share record. * Providing a list of all public keys and share IDs for all shares of the given item via this endpoint   Getting this list is the first step in updating all shares of the item.
      * Prepare an update of all shares of one item
      */
-    itemsIdSharesGet(id, meecoDelegationId, meecoOrganisationId, initOverrides) {
+    itemsItemIdSharesGet(itemId, meecoDelegationId, meecoOrganisationId, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.itemsIdSharesGetRaw({ id: id, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
+            const response = yield this.itemsItemIdSharesGetRaw({ itemId: itemId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
             return yield response.value();
         });
     }
@@ -376,10 +376,10 @@ class SharesApi extends runtime.BaseAPI {
      * Share your item with connected users.  Each share can be a share of all slots of the item, in that case `slot_id` is `NULL`, or it can be a share of just one slot. In this case `slot_id` references one of the slots of the item.  There are 3 users involved in each share:  * owner - the owner of the shared item * sender -  the user who shares data. Can be the owner or one of the recipients * recipient - the user who recieves the shared data.   Whether a non-owner may on-share a shared slot is defined in field `onsharing_permitted`.  Only the owner of the item can set `onsharing_permitted` to `true`. If `onsharing_permitted` is `false`, the recipient may on-share the item, but when that recipient creates an on-share, `onsharing_permitted` in that on-share is forced to be `false`. In other words, the depth of on-sharing in limited to 3:       OWNER ==> RECIPIENT AND SENDER ==>  RECIPIENT    Some shares require that the recipient accepts the terms of the share. Until the terms are not accepted the share DEK is hidden.   Data in slots is initially encrypted with the DEK in field `encrypted_dek`. The DEK in `encrypted_dek` is encrypted with the public key of the share recipient. When processing a share the client application is expected to decrypt the slot data and re-encrypt with the private DEK.  A public key of the recipient is needed to encrypt the share DEK. Updating all shares of the same item is performed by the owner in one go. In a situation when a share has been created by a recipient, not the owner, and there is no connection between the owner and the recipient, the owner has no access to a public key of the recipient. In order to address this problem when a share is created we also add fields `public_key` and `keypair_external_id` from the connection record between the recipient and the sender. `keypair_external_id` identifies the keypair that the public key belongs to.  When a recipient of a share on-shares the data with someone else, nothing prevents him/her to encrypt some other data instead of the original data. We need a way to enforce integrity of on-shares. We do this with help of HMAC - hash-based message authentication code obtained by running a cryptographic hash function over the data and a shared secret key.    Two fields in each slot are used for this purpose: * `encrypted_value_verification_key` - is a value verification key encrypted in the same way as the value itself: with the share DEK * `value_verification_hash` - the result of the HMAC function run on the slot value using `encrypted_value_verification_key`. `value_verification_hash` is stored as-is, unencrypted.   Only the owner of the data may send `value_verification_hash` when creating or updating the share. When other senders create a share, `value_verification_hash` must be `NULL`.  `encrypted_value_verification_key` may and should be sent by every sender, owner or not, because `encrypted_value_verification_key` must be re-encrypted with the share DEK for each share.  If the sender replaces `encrypted_value_verification_key` and/or the slot value, this will break the client-side verification against `encrypted_value_verification_key`. Field `encrypted_value` may be `NULL`. If `encrypted_value` is `NULL`, then `encrypted_value_verification_key` and `value_verification_hash` may also be `NULL`. If `encrypted_value` is present, then `encrypted_value_verification_key` and `value_verification_hash` are mandatory.
      * Share your item with connected users
      */
-    itemsIdSharesPostRaw(requestParameters, initOverrides) {
+    itemsItemIdSharesPostRaw(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            if (requestParameters.id === null || requestParameters.id === undefined) {
-                throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling itemsIdSharesPost.');
+            if (requestParameters.itemId === null || requestParameters.itemId === undefined) {
+                throw new runtime.RequiredError('itemId', 'Required parameter requestParameters.itemId was null or undefined when calling itemsItemIdSharesPost.');
             }
             const queryParameters = {};
             const headerParameters = {};
@@ -398,7 +398,7 @@ class SharesApi extends runtime.BaseAPI {
                 }
             }
             const response = yield this.request({
-                path: `/items/{id}/shares`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))),
+                path: `/items/{item_id}/shares`.replace(`{${"item_id"}}`, encodeURIComponent(String(requestParameters.itemId))),
                 method: 'POST',
                 headers: headerParameters,
                 query: queryParameters,
@@ -411,9 +411,9 @@ class SharesApi extends runtime.BaseAPI {
      * Share your item with connected users.  Each share can be a share of all slots of the item, in that case `slot_id` is `NULL`, or it can be a share of just one slot. In this case `slot_id` references one of the slots of the item.  There are 3 users involved in each share:  * owner - the owner of the shared item * sender -  the user who shares data. Can be the owner or one of the recipients * recipient - the user who recieves the shared data.   Whether a non-owner may on-share a shared slot is defined in field `onsharing_permitted`.  Only the owner of the item can set `onsharing_permitted` to `true`. If `onsharing_permitted` is `false`, the recipient may on-share the item, but when that recipient creates an on-share, `onsharing_permitted` in that on-share is forced to be `false`. In other words, the depth of on-sharing in limited to 3:       OWNER ==> RECIPIENT AND SENDER ==>  RECIPIENT    Some shares require that the recipient accepts the terms of the share. Until the terms are not accepted the share DEK is hidden.   Data in slots is initially encrypted with the DEK in field `encrypted_dek`. The DEK in `encrypted_dek` is encrypted with the public key of the share recipient. When processing a share the client application is expected to decrypt the slot data and re-encrypt with the private DEK.  A public key of the recipient is needed to encrypt the share DEK. Updating all shares of the same item is performed by the owner in one go. In a situation when a share has been created by a recipient, not the owner, and there is no connection between the owner and the recipient, the owner has no access to a public key of the recipient. In order to address this problem when a share is created we also add fields `public_key` and `keypair_external_id` from the connection record between the recipient and the sender. `keypair_external_id` identifies the keypair that the public key belongs to.  When a recipient of a share on-shares the data with someone else, nothing prevents him/her to encrypt some other data instead of the original data. We need a way to enforce integrity of on-shares. We do this with help of HMAC - hash-based message authentication code obtained by running a cryptographic hash function over the data and a shared secret key.    Two fields in each slot are used for this purpose: * `encrypted_value_verification_key` - is a value verification key encrypted in the same way as the value itself: with the share DEK * `value_verification_hash` - the result of the HMAC function run on the slot value using `encrypted_value_verification_key`. `value_verification_hash` is stored as-is, unencrypted.   Only the owner of the data may send `value_verification_hash` when creating or updating the share. When other senders create a share, `value_verification_hash` must be `NULL`.  `encrypted_value_verification_key` may and should be sent by every sender, owner or not, because `encrypted_value_verification_key` must be re-encrypted with the share DEK for each share.  If the sender replaces `encrypted_value_verification_key` and/or the slot value, this will break the client-side verification against `encrypted_value_verification_key`. Field `encrypted_value` may be `NULL`. If `encrypted_value` is `NULL`, then `encrypted_value_verification_key` and `value_verification_hash` may also be `NULL`. If `encrypted_value` is present, then `encrypted_value_verification_key` and `value_verification_hash` are mandatory.
      * Share your item with connected users
      */
-    itemsIdSharesPost(id, meecoDelegationId, meecoOrganisationId, postItemSharesRequest, initOverrides) {
+    itemsItemIdSharesPost(itemId, meecoDelegationId, meecoOrganisationId, postItemSharesRequest, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.itemsIdSharesPostRaw({ id: id, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, postItemSharesRequest: postItemSharesRequest }, initOverrides);
+            const response = yield this.itemsItemIdSharesPostRaw({ itemId: itemId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, postItemSharesRequest: postItemSharesRequest }, initOverrides);
             return yield response.value();
         });
     }
@@ -421,10 +421,10 @@ class SharesApi extends runtime.BaseAPI {
      * Updating all shares of one item is done by the item owner in one go.  Before calling this endpoint the client application is expected to retrieve the list of shares IDs and public keys via `GET /items/{id}/shares`.  The POST body of this endpoint contains  * a list of share DEKs encrypted with public keys of share recipients * a list of slot values for each slot and each share, each encrypted with the DEK of the share that the slot belongs to  * Optionally: a list of completed `ClientTask` tasks  When a recipient of a share on-shares the data with someone else, nothing prevents him/her to encrypt some other data instead of the original data. We need a way to enforce integrity of on-shares. We do this with help of HMAC - hash-based message authentication code obtained by running a cryptographic hash function over the data and a shared secret key.    Two fields in each slot are used for this purpose: * `encrypted_value_verification_key` - is a value verification key encrypted in the same way as the value itself: with the share DEK * `value_verification_hash` - the result of the HMAC function run on the slot value using `encrypted_value_verification_key`. `value_verification_hash` is stored as-is, unencrypted.   Only the owner of the data may send `value_verification_hash` when creating or updating the share. When other senders create a share, `value_verification_hash` must be `NULL`.  `encrypted_value_verification_key` may and should be sent by every sender, owner or not, because `encrypted_value_verification_key` must be re-encrypted with the share DEK for each share.  If the sender replaces `encrypted_value_verification_key` and/or the slot value, this will break the client-side verification against `encrypted_value_verification_key`.  Field `encrypted_value` may be `NULL`. If `encrypted_value` is `NULL`, then `encrypted_value_verification_key` and `value_verification_hash` may also be `NULL`. If `encrypted_value` is present, then `encrypted_value_verification_key` and `value_verification_hash` are mandatory.
      * Update all shares of one item
      */
-    itemsIdSharesPutRaw(requestParameters, initOverrides) {
+    itemsItemIdSharesPutRaw(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            if (requestParameters.id === null || requestParameters.id === undefined) {
-                throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling itemsIdSharesPut.');
+            if (requestParameters.itemId === null || requestParameters.itemId === undefined) {
+                throw new runtime.RequiredError('itemId', 'Required parameter requestParameters.itemId was null or undefined when calling itemsItemIdSharesPut.');
             }
             const queryParameters = {};
             const headerParameters = {};
@@ -443,7 +443,7 @@ class SharesApi extends runtime.BaseAPI {
                 }
             }
             const response = yield this.request({
-                path: `/items/{id}/shares`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))),
+                path: `/items/{item_id}/shares`.replace(`{${"item_id"}}`, encodeURIComponent(String(requestParameters.itemId))),
                 method: 'PUT',
                 headers: headerParameters,
                 query: queryParameters,
@@ -456,9 +456,9 @@ class SharesApi extends runtime.BaseAPI {
      * Updating all shares of one item is done by the item owner in one go.  Before calling this endpoint the client application is expected to retrieve the list of shares IDs and public keys via `GET /items/{id}/shares`.  The POST body of this endpoint contains  * a list of share DEKs encrypted with public keys of share recipients * a list of slot values for each slot and each share, each encrypted with the DEK of the share that the slot belongs to  * Optionally: a list of completed `ClientTask` tasks  When a recipient of a share on-shares the data with someone else, nothing prevents him/her to encrypt some other data instead of the original data. We need a way to enforce integrity of on-shares. We do this with help of HMAC - hash-based message authentication code obtained by running a cryptographic hash function over the data and a shared secret key.    Two fields in each slot are used for this purpose: * `encrypted_value_verification_key` - is a value verification key encrypted in the same way as the value itself: with the share DEK * `value_verification_hash` - the result of the HMAC function run on the slot value using `encrypted_value_verification_key`. `value_verification_hash` is stored as-is, unencrypted.   Only the owner of the data may send `value_verification_hash` when creating or updating the share. When other senders create a share, `value_verification_hash` must be `NULL`.  `encrypted_value_verification_key` may and should be sent by every sender, owner or not, because `encrypted_value_verification_key` must be re-encrypted with the share DEK for each share.  If the sender replaces `encrypted_value_verification_key` and/or the slot value, this will break the client-side verification against `encrypted_value_verification_key`.  Field `encrypted_value` may be `NULL`. If `encrypted_value` is `NULL`, then `encrypted_value_verification_key` and `value_verification_hash` may also be `NULL`. If `encrypted_value` is present, then `encrypted_value_verification_key` and `value_verification_hash` are mandatory.
      * Update all shares of one item
      */
-    itemsIdSharesPut(id, meecoDelegationId, meecoOrganisationId, putItemSharesRequest, initOverrides) {
+    itemsItemIdSharesPut(itemId, meecoDelegationId, meecoOrganisationId, putItemSharesRequest, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.itemsIdSharesPutRaw({ id: id, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, putItemSharesRequest: putItemSharesRequest }, initOverrides);
+            const response = yield this.itemsItemIdSharesPutRaw({ itemId: itemId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, putItemSharesRequest: putItemSharesRequest }, initOverrides);
             return yield response.value();
         });
     }