๐Backup methods
A guide that goes over all of the various backup methods your users can use.
Passkey + Enclave Backup
Allow customers to create a native passkey on their device that is used to authenticate into a secure enclave that holds the encryption key for the user. Customer's passkeys are backed up to the native cloud storage for their device.
Implementation Requirements
Initialize passkey storage as a backup option in the Portal Config Object.
Configuring the relying party
Use Portal as your relying party
Add
portalhq.io
as a web credential domain in your app.Share your app bundle id with the Portal Team.
Use your own domain as the relying party
Ensure you have set up your associate domain correctly in your app and that you are serving an aasa file from whatever your relying party domain is set to. You will need to be sure you have the webcredential
field set properly for your app in your aasa file.
Resources from apple:
Relying party
A relying party is a trusted domain that is tied to the public key credentials of your users for their passkey . We offer the option to use portalhq.io
as your relying party domain. It requires you to add portalhq.io
as an Associated Domain in your iOS application and share your team id + application bundle id. If you already have your domain as a webcredential
for your application then you can simply pass in your domain as the relying party and everything should work.
Password/Pin Backup
Allow customers to create a password/pin. Customers can either remember the password or store it in a password storage manager.
Implementation Requirements
Create a UI for password input.
Enforce password requirements. Customer can choose between password, PIN code, passcode, or any other text-based input.
If user forgets password there are no additional recovery options.
iCloud
See the docs on how to Configure iCloud Storage.
Google Drive
See the docs on how to Configure Gdrive Storage.
Last updated