Backup methods
A guide that goes over all of the various backup methods your users can use.
Last updated
A guide that goes over all of the various backup methods your users can use.
Last updated
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.
Initialize passkey storage as a backup option in the Portal Config Object with the correct origin
Configuring the relying party
You have two options when it comes to relying party configurations. It is important that you understand the implications of this decision. 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 a trusted domain in your manifest file in your android application and share your applications SHA fingerprint and namespace with our team. We will add them to our own digital asset links file and that will allow your app to set portalhq.io
as the relying party.
Add portalhq.io
as an included domain in your manifest file.
Share your applications SHA fingerprint and namespace with the Portal Team.
Ensure you have set up your digital asset links url correctly in your app and that you are serving a digital asset links file from the URL you specified in the asset statement in your manifest file.
Read more about setting this up from the android docs:
Regardless of the relying party decision you make above, you will need to set the relying party origin to:
Initializing the passkey storage class
Calling backup
Allow customers to create a password/pin. Customers can either remember the password or store it in a password storage manager.
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.
If you do not pass in a backup option into portal.backupWallet()
we will default to GDRIVE
backup.
read more info on how to get the SHA256 hash of the apk signing cert.
See the docs on how to .