Skip to content

Releases: openfort-xyz/shield-js

0.1.27

26 Sep 17:31
3906adb
Compare
Choose a tag to compare

What

Add OTP required error processing

0.1.26

22 Sep 14:10
38377f7
Compare
Choose a tag to compare

What

This release adds a new method to get share by reference. It calls a brand new API endpoint.

0.1.25

09 Sep 14:54
Compare
Choose a tag to compare
v0.1.25

fix: add package-lock

0.1.24

05 Sep 10:08
e133138
Compare
Choose a tag to compare

Add passkeyReference field in Share , allowing users to specify passkey-related information when registering a share.

passkeyReference contains passkey_id and, optionally, passkey_env.

passkey_env will be automatically calculated by Shield by reading the User-Agent header if not specified.

Add two new methods

public async getEncryptionMethodsBySignerReferencesDetailed(auth: ShieldAuthOptions, signers: string[], requestId?: string): Promise<Map<string, RecoveryMethod>>
public async getEncryptionMethodsByOwnerIdDetailed(auth: ShieldAuthOptions, users: string[], requestId?: string): Promise<Map<string, RecoveryMethod>>

And the following models

export interface PasskeyEnv {
    name?: string;
    os?: string;
    osVersion?: string;
    device?: string;
}

export interface RecoveryMethodDetails {
    passkeyId: string;
    passkeyEnv?: PasskeyEnv;
}

export interface RecoveryMethod {
    method: string;
    details?: RecoveryMethodDetails;
}

Allowing users to retrieve detailed encryption details including passkey_id and passkey_env if the share happens to be encrypted via passkeys.

The other two already existing methods (i.e. the ones without the Detailed suffix) will still return only the encryption_type value for every key (reference/userID).

These two new methods can be safely used against older shield versions and nothing will break: both bulk endpoints were already returning a Map<string, Map<string, string>> anyway.

0.1.23

29 Aug 17:37
Compare
Choose a tag to compare

Wrap HTTP calls with axios & axios-retry.

Make calls to Shield have a backoff strategy consisting of three retries after 0.5, 1, and 2 seconds respectively.

Do it only for idempotent calls and if the cause of failure was due to network issues (e.g. ERRCONREFUSED) or status codes >= 500 (server error, bad gateway, etc).

0.1.22

29 Aug 08:29
Compare
Choose a tag to compare

Fix Map treatment in bulk endpoints.
Fix requestId parameter order + made it optional.

0.1.21

29 Aug 06:52
Compare
Choose a tag to compare

Change hashmap parsing for shares/encryption/reference/bulk and shares/encryption/user/bulk.

0.1.20

28 Aug 18:12
Compare
Choose a tag to compare

Add support for

shares/encryption/reference/bulk
shares/encryption/user/bulk

0.1.19

26 Aug 11:25
Compare
Choose a tag to compare
v0.1.19

chore: bump to 0.1.19

0.1.18

26 Aug 08:52
f0823ad
Compare
Choose a tag to compare

Add passkey entropy source