Using MFA for Mobile Application

single connect’s built in mfa can be used as a secondary layer of authentication for logging into the mobile application for its online features (approval management, geo fencing, and password manager) to enable mfa for mobile applications admin and user must install the single connect mobile app and register a token to receive offline tokens with the mobile app (you get the offline tokens from the offline token > add > register token menu) mfa must be enabled for the user group that will be using mfa for mobile application connections (see sections docid\ n5h8lvfjlvnlnbg1lxfs6 , docid\ myq5n bfc pn84wbrvmal , docid\ u2oncfg32vjondgob1t5r navigate to administration > system config man set the mobile application otp enabled parameter as true after these settings are done and a login operation was started on the mobile application, the application will automatically look for a registered token in its offline tokens with the name that matched the tfa otp issuer parameter if there is a registered token with another name, then it will prompt the user to change a registered token the user selects yes and enters a new token on the next page window forward to the token page for entering a new token if the token is matched the user can log in once the current six digit value of the offline token is validated with the server, login will be successful if there’s no registered token in the mobile application and mfa is enabled with the parameter above, registering a token also requires a multi factor authentication the system will send a one time password (otp) to the user’s phone number the user will be asked to enter the otp on his/her mobile application the mobile application mfa functionality works only with the registered tokens to ensure that the offline tokens are only working in one application at a time