Skip to main content

OrganizationUsersKeysApi

bitwarden_api_api::apis::organization_users_keys_api

Trait OrganizationUsersKeysApi 

Source 
pub trait OrganizationUsersKeysApi: Send + Sync {
    // Required methods
    fn get_pending_v2_upgrades<'a, 'life0, 'async_trait>(
        &'life0 self,
        org_id: Uuid,
        continuation_token: Option<Uuid>,
    ) -> Pin<Box<dyn Future<Output = Result<OrganizationUserPendingV2UpgradeResponseModelListResponseModel, Error>> + Send + 'async_trait>>
       where Self: 'async_trait,
             'a: 'async_trait,
             'life0: 'async_trait;
    fn post_v2_upgrades<'a, 'life0, 'async_trait>(
        &'life0 self,
        org_id: Uuid,
        organization_user_v2_upgrades_request_model: Option<OrganizationUserV2UpgradesRequestModel>,
    ) -> Pin<Box<dyn Future<Output = Result<(), Error>> + Send + 'async_trait>>
       where Self: 'async_trait,
             'a: 'async_trait,
             'life0: 'async_trait;
}

Required Methods§

Source

fn get_pending_v2_upgrades<'a, 'life0, 'async_trait>( &'life0 self, org_id: Uuid, continuation_token: Option<Uuid>, ) -> Pin<Box<dyn Future<Output = Result<OrganizationUserPendingV2UpgradeResponseModelListResponseModel, Error>> + Send + 'async_trait>>
where Self: 'async_trait, 'a: 'async_trait, 'life0: 'async_trait,

GET /organizations/{orgId}/users/keys/pending-v2-upgrades A V1 to V2 upgrade rotation cannot re-wrap the account recovery key, because that requires the member to trust the organization’s public key and the upgrade does not prompt the member. The rotation leaves a V2 upgrade token on the membership instead. Account recovery gives the admin the member’s V1 user key, so the admin unwraps the V2 user key from the token and re-wraps the account recovery key with it. Only Owners and Admins of the organization can call this endpoint. It returns only the members the caller can recover. The client posts each page to POST v2-upgrades, then reads the next page with the continuation token of the response, until the token is null. A page can be empty and still have a token.

Source

fn post_v2_upgrades<'a, 'life0, 'async_trait>( &'life0 self, org_id: Uuid, organization_user_v2_upgrades_request_model: Option<OrganizationUserV2UpgradesRequestModel>, ) -> Pin<Box<dyn Future<Output = Result<(), Error>> + Send + 'async_trait>>
where Self: 'async_trait, 'a: 'async_trait, 'life0: 'async_trait,

POST /organizations/{orgId}/users/keys/v2-upgrades Only Owners and Admins of the organization can call this endpoint, and only for members they can recover. A membership that has changed since the read is skipped rather than rejected.

Dyn Compatibility§

This trait is dyn compatible.

In older versions of Rust, dyn compatibility was called "object safety".

Implementors§