![]() This shared key is initially generated by the service provider and added to the app during enrollment.Īs the service provider, you can provide Google Authenticator support to your users by enabling it in your Okta org and building out support for it in your application using the Embedded SDK. The service provider independently generates the password and validates that the submitted password is identical to the generated one.Ī shared key linking the Google Authenticator app and service provider allows for both entities to generate the same password. Google Authenticator generates the TOTP, which is submitted by the user to the service provider for verification. Authentication flowĪfter a user is enrolled in Google Authenticator, they are challenged by the service provider (for example, a website) to provide a time-based one-time passcode (TOTP) during authentication. It doesn't require a cellular or Wifi network to use and setup can be as easy as a snapshot of a QR Code. It's considered more secure than other additional authenticators such as SMS since it's resistant to SIM swap attacks. The app is often used in conjunction with a password to strengthen user accounts from security attacks. ![]() Google Authenticator is an authenticator app developed by Google used to verify the identity of a user. The reason to choose Google Authenticator Sample ASP.NET MVC Application using Embedded Authentication with the IDX SDK (opens new window)
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |