Skip to content

Commit

Permalink
Release 14.39.1
Browse files Browse the repository at this point in the history
  • Loading branch information
github-actions[bot] committed Nov 20, 2024
1 parent 9871590 commit c30a736
Show file tree
Hide file tree
Showing 2 changed files with 42 additions and 3 deletions.
23 changes: 20 additions & 3 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,16 +4,33 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/)
and this project adheres to [Semantic Versioning](https://semver.org/).

## 14.39.1 - 2024-11-20

## 14.39.0 - 2024-11-18
### Added
- Warning to push usage of Studio token over SDK token and deprecation message
- New accessible autocomplete component
- New accessible autocomplete component

### Changed
- adds smart caret false for OTP phone input
- adds smart caret false for OTP phone input

### Removed
- Removed debug log from production build

### Fixed
- Fix type exports
- Provided a more descriptive cross-device error screen

## 14.38.0 - 2024-09-30
### Fixed
- Fixed QR code from showing during re-connection phase
- Fix navigation bug related to consent in classic mode
- Fixed navigation bug related to consent in classic mode
- Removed the 10s timeout for the loading of modules
- Implement cross_device_url for enterprise clients
- Removed redundant video upload in document capture
- add side, issuing_country and type to the video upload
- Removed redundant video upload in document capture
- add side, issuing_country and type to the video upload

## 14.37.1 - 2024-09-19
### Fixed
Expand Down
22 changes: 22 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -1196,6 +1196,28 @@ The callbacks return a `FormData` object, including the information that the SDK
}
```

### Custom biometric token storage

When using the decentralized authentication solution, by default the SDK manages biometric token storage, by storing it on local storage. The SDK also allows the clients to take control of the token lifecycle and exposes an callback to override the default implementation to read and write the token, so it can be stored on device, in cloud, in a keystore or on your premises.

**Note** that by using the callback it will prevent the SDK to store the token.

```typescript
Onfido.init({
...
onBiometricTokenGenerated: (customerUserHash: string, biometricToken: string): void => {
// Called when new biometric token is generated during onboarding
// Use this callback to securely store the biometric token
// Please ensure that customerUserHash to biometricToken relationship is 1:1
},
onBiometricTokenRequested: (customerUserHash: string): Promise<string> => {
// Called when biometric token is requested during re-authentication
// Once you have the token, resolve the promise with it
return Promise.resolve('biometricToken')
}
});
```

#### Uploading the media files to Onfido

By default, this feature will prevent the request from being sent to Onfido, requiring you to [manually upload](https://documentation.onfido.com/api/latest#upload-document) the media files to Onfido from your backend for further processing.
Expand Down

0 comments on commit c30a736

Please sign in to comment.