This article explains how to modify the labels within the Okta Sign-In Widget to generalize the "Google Authenticator" factor, indicating to end users that other Authenticator apps that support Time-based One-time Password (TOTP) can be used, not just the dedicated Google Authenticator app.
- Custom Okta Sign-In Widget (Okta hosted or self-hosted)
- Google Authenticator
The Okta Widget is designed to say "Google Authenticator" for any view where a user can be challenged or enroll in a TOTP factor/authenticator.
To modify the labels shown in the widget when a user enrolls or verifies using a TOTP factor, use the widget's i18n object to update the text.
Okta Classic
If in an Okta Classic org, with useInteractionCodeFlow disabled (widget versions 5.x and 6.x) or useClassicEngine enabled (widget version 7.x+), then the following i18n keys are used when challenging/enrolling in the TOTP factor:
factor.totpSoft.googleAuthenticatorenroll.totp.setupGoogleAuthAppenroll.totp.manualSetupInstructionsenroll.totp.manualSetupInstructions.genericenroll.totp.manualSetupInstructions.specific
Example of what these modifications could look like in the Okta-hosted widget when updating the values for these keys in English:
if (config.i18n.en){
config.i18n.en["factor.totpSoft.googleAuthenticator"] = "Authenticator app"
config.i18n.en["enroll.totp.setupGoogleAuthApp"] = "Launch {0} and select the option to scan a barcode/QR code"
config.i18n.en["enroll.totp.manualSetupInstructions"] = "To set up manually enter your Okta Account username and then input the following in the Secret Key Field" // this is the original text
config.i18n.en["enroll.totp.manualSetupInstructions.generic"] = "To set up manually enter your Account username and then input the following in the Secret Key Field" // this is the original text
config.i18n.en["enroll.totp.manualSetupInstructions.specific"] = "To set up manually enter your {0} Account username and then input the following in the Secret Key Field" // this is the original text
}
Okta Identity Engine
If in an Okta Identity Engine org that has useInteractionCodeFlow enabled (widget versions 5.x and 6.x) or useClassicEngine disabled (widget version 7.x+), then the following i18n keys are used when challenging/enrolling in the TOTP factor:
oie.google_authenticator.labeloie.google_authenticator.authenticator.descriptionoie.enroll.google_authenticator.setup.titleoie.enroll.google_authenticator.scanBarcode.descriptionoie.verify.google_authenticator.otp.titleoie.verify.google_authenticator.otp.descriptionoie.enroll.google_authenticator.manualSetupInstructions
Example of what these modifications could look like in the Okta-hosted widget when updating the values for these keys in English:
if (config.i18n.en){
config.i18n.en["oie.google_authenticator.label"] = "Authenticator app"
config.i18n.en["oie.google_authenticator.authenticator.description"] = "Enter a temporary code generated from your authenticator app."
config.i18n.en["oie.enroll.google_authenticator.setup.title"] = "Set up Authenticator app"
config.i18n.en["oie.enroll.google_authenticator.scanBarcode.description"] = "Launch your authenticator app and choose to add an account by scanning a barcode or QR code"
config.i18n.en["oie.verify.google_authenticator.otp.title"] = "Verify with an authenticator app"
config.i18n.en["oie.verify.google_authenticator.otp.description"] = "Enter the temporary code generated in your authenticator app"
config.i18n.en["oie.enroll.google_authenticator.manualSetupInstructions"] = "To set up manually enter your Okta Account username and then input the following in the Secret Key Field" // this is the original text
}
NOTE: The oie.enroll.google_authenticator.scanBarcode.description and oie.enroll.google_authenticator.manualSetupInstructions Widget labels in Okta Identity Engine are specific to Google and how to set up the application.
