I have been reviewing the ACUL samples repo and noticed after drilling down into the handleEnroll call in useMFABeginEnrollOptionsManager hook that the payload.action must be of type MfaEnrollFactorType which does not include ‘webauthn-platform’. I am looking to have ACUL enroll device biometrics and I would need ‘webauthn-platform’ option added to do so. Is there a reason ‘webauthn-platform’ was added to MfaLoginFactorType but not MFAEnrollFactorType? Can the nested enroll call handle ‘webauthn-platform’ correctly if I were to change the implementation of this handleEnroll call to account for this missing value?
After looking closer at the handleEnroll call, it doesn’t look like I have the flexibility to change the handleEnroll call to allow ‘webauthn-platform’ either since the @auth0/auth0-acul-react/mfa-begin-enroll-options enroll function expects a MFAEnrollFactorType. I also noticed that my IDE is pushing me towards a mock implementation of enroll as well so maybe this hook is not functionally complete yet? Just looking to understand, thanks!!
Welcome to the Auth0 Community!
I am sorry about the delayed response to your question.
What I believe you are looking for is to use the MFA-WebAuthn-Platform-Enrollment screen for webauth enrollment instead of relying on the mentioned hook. You would need to use the dedicated screen instead of using the API to enroll users.
Let me know if you have any other questions!
Kind Regards,
Nik