4
Allow the friendly name of an existing MFA factor to be updated/amended
Source: supabase/supabase#36657 · opened by @SteveHawes
Currently, the friendly name of an MFA factor must be set when enrolling the factor and it cannot be changed once enrolled. This gives the problem that if a user is trying to enrol a TOTP factor, they will need to provide the friendly name before they see the QR code as this is only returned in the result of the enrolment call.
I would like to have an additional method that allows the application update or amend the friendly name by specifying the factorId and the new value for the friendly name. I am currently developing with the Flutter library so the code would be something like:
final AuthMFAUpdateResponse result = await supabase.auth.mfa.updateFactor(factorId: factorId, friendlyName: newValue);
The result could return the old value in case that is required by the developer.
I would like to have an additional method that allows the application update or amend the friendly name by specifying the factorId and the new value for the friendly name. I am currently developing with the Flutter library so the code would be something like:
final AuthMFAUpdateResponse result = await supabase.auth.mfa.updateFactor(factorId: factorId, friendlyName: newValue);
The result could return the old value in case that is required by the developer.
No pledges yet. Be the first to back this.
Comments
Similar requests
Auth: Auto-enforce AAL2 at API gateway level for MFA-enrolled users
1 vote · 0 comments
Enable detecting which TOTP was used for MFA
3 votes · 0 comments
Provide option to set up 2FA/MFA with REST APIs
2 votes · 0 comments
Add support for Backup/recovery codes as MFA
11 votes · 0 comments
Email as a second factor in MFA
13 votes · 0 comments
No comments yet.