Demo: SAML Integrations (Vault & Fill & Assigning Applications)

Speaker 1: We will now show the configuration of two vault and fill apps. The first will be an app that's in Oka's industry leading catalog of over 5,000. The second will be an app that's not in our catalog. In both cases, Okta employs a proven SSO browser plugin that's heuristics-based, so it's self-healing. What this means is that, if a website's login page changes, the plugin will be able to intelligently detect it and post the credentials without issue. Nothing needs to change on the Okta side.

Speaker 1: I'll go ahead and add [Teladoc 00:00:00:28]. This will be our first application. I'll then get to choose the application visibility and then I'll also get to choose whether or not to sign the user in automatically.

Speaker 1: Next, I'll choose how to allow the user or the admin to set the username and password. I can give the user full autonomy as seen here, or I can have the administrators set the username and password and maybe hide those credentials from the end user. This may be useful for the case of, let's say, a shared Twitter account. Finally, I'll choose whether or not to allow the user to see the password. Then I can assign the user to the app. I'm going to skip this step for now. And that's it. Very simple.

Speaker 1: Oka's catalog is the most comprehensive in terms of breadth and depth as you can see here, but we haven't added all applications yet, as the list keeps growing. If you can't find an app, we provide a wizard-driven approach that allows you to quickly and easily add new apps. Let's see this in action. I've been hearing a lot about this application called Sofi. Apparently it's a loan or mortgage application and I don't see it in Okta, so let's go ahead and create it.

Speaker 1: It is a secure web authentication app, meaning this is Oka's terminology for fault and fill