Exporting Multiple Custom TOTP Authenticators from a Legacy On-Prem System to Okta via an API Call
Last Updated:
Overview
This article addresses the question: Can one or multiple temporary one time password (TOTP) authenticators be exported from an on-prem legacy system to Okta via an API call?
Applies To
- API calls
- Multi-factor Authentication
- Okta Identity Engine (OIE)
Cause
Solution
One or more TOTP factors must be first configured in Okta, and only after the configuration is done, the enrollment and activation can be done via an API call. Therefore, creating multiple custom TOTP authenticators in Okta from a legacy on-prem system via an API call is not yet possible, as Okta does not have endpoints that can provide API calls to generate multiple TOTP factors and profile IDs. Also, there is no API call to export multiple Factor Profile IDs in bulk from Okta's Admin console. Each custom TOTP authenticator must be recreated in Okta and only then enrolled and activated via an API call.
For more information about how to configure and enroll a custom TOTP factor, please check the Related References section.
