Android Updates: Auth Required, Device Credential Fallback Added, and Error Codes Fixed and Consolidated

[brian-weasner]

MOST OF THE CHANGES ARE DUE TO THE ADDED .gitignore

Should Fix The Following Issues:

• catch of verifyIdentity is not returning the error code #69
• Feature request : Invalidate password on enrollment #72
  • Related: Missed database check #51
• useFallback:true #76
• Android: Able to get credentials without verifying/authorizing user with biometrics #80
• [Security Enhancement] Android: Enable StrongBox (Api 28 and Newer) #81

Overview of changes

Breaking!

• Android
  • If your device has device level credentials, you are required to be authenticated before being able to get/set/delete credentials.
  • Your encypt/decrypt key will become invalided on biometric enrollment changes.
  • Error structure and error codes for verification will be the same as iOS

Thank You

Thank you for making this plugin! Let me know what you think of these changes. If there are any changes you want me to make I will promptly make them so that we can get this merged and deployed quickly.

[brian-weasner]

Do not merge yet, I found odd error.
After enrolling new biometric, the key becomes invalidated and after I delete the key and re-auth and then create a new key I'm still getting Key user not authenticated

[brian-weasner]

I believe some discussion needs to be had about how we want to handle configuration of the Keys.

1. Do we want to default everyone using this plugin to default to Biometric auth being forced before any get/set/delete of the credentials?

   • I assume we want this to be configurable.
     • What function do we want to use to configure it?
     • If do we want a configuration object that must be provided before any call is made within the plugin?
   • Is there a similar setting for iOS or is this Android Specific?

2. Similar to the above do we want to force biometric enrollment to automatically invalidate the current encrypt/decrypt key?

   • I assume we want this to be configurable? Via set? Via config?
   • iOS?

[brian-weasner]

Umm, not sure you wanted this to get merged? I set this as a draft due to the error I got regarding the Key user not authenticated #83 (comment)

[brian-weasner]

Actually, looking at commit history I removed setUserAuthenticationRequired which is what seemed to be causing the Key user not authenticated error, so this shouldn't break master branch