Create an MFA authenticator in RPA Hub
- UpdatedJul 31, 2025
- 2 minutes to read
- Zurich
- RPA Hub
Define the authenticator and token length that acts as an enabler for the Time-based One-time Password (TOTP) authentication in RPA Hub so that the unattended robots can seamlessly authenticate against multi-factor authentication (MFA)-enabled applications.
Before you begin
Familiarize yourself with multi-factor authentication (MFA) concepts. For more information, see Multi-factor Authentication.
Familiarize yourself with the TOTP authentication in RPA Hub. For more information, see TOTP authentication in RPA Hub.
You must do this task in the classic environment.
Role required: sn_rpa_fdn.rpa_release_manager or sn_rpa_fdn.rpa_admin
About this task
- Google Authenticator
- Microsoft Authenticator
- Okta Verify
The MFA authenticator record acts as an input to the Time-based One-time Password (TOTP) authenticator.
After you create an MFA authenticator record, all the fields are read-only.
You can't edit an MFA authenticator record. If changes are required to an existing MFA record, you must retire an existing record and then create an MFA authenticator record.
Procedure
What to do next
Create a TOTP authenticator. For more information, see Create a TOTP authenticator in RPA Hub.
Related Content
- Retire an MFA authenticator in RPA Hub
Retire a multi-factor authentication (MFA) authenticator in RPA Hub so that you can turn off the authentication. After you retire an MFA authenticator, it can’t be used again.
- Delete a TOTP authenticator in RPA Hub
Delete a Time-based One-time Password (TOTP) authenticator record in RPA Hub so that you can dissociate it from a bot process.