feat: how should we manage app user configuration defaults #6
Labels
area : api
Pertaining to application programming interfaces
area : front-end
Pertaining to adaptive user interface composition, stylings, experiences, and integration with APIs
area : tooling
Pertaining to tooling and configuration of project infrastructure
In the event that a user does not have a mobile device with biometric sensors, they have other preferred methods of multi-factor authentication, or they want extra layers of security and fallback methods with which to authenticate, we need to come up with a list of other services or capabilities in order to provide user choice in applications that implement this package.
What level of app user configuration should be supported to opt-in to MFA?
Ideally, iVault includes API to support all of these opt-in options for users and/or based on application configuration with graceful fallback if necessary.
The text was updated successfully, but these errors were encountered: