<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D50Z00008G7V11SAFOkta Classic EngineDevices and MobilityAnswered2024-04-30T09:18:25.000Z2015-09-17T19:44:30.000Z2016-10-03T09:22:25.000Z
What is the suggested way to authenticate users through a pure HTML5/Javascript client application?
We have a number of ASP MVC applications hooked up to OKTA, but we're unsure of the best way to connect a pure HTML5/Javascript application that's currently in development.

 

This application could be hosted as a website, but also compiled into a hybrid app to run on mobile phones (using Cordova most likely)...

 

So in a situation like this, what would be the BEST way to authenticate users with OKTA? 

 

Do I need to setup an endpoint on a server somewhere that can turn SAMLrequests into Oauth tokens? 


  • j5v7c (j5v7c)

    Original Author: Patrick Kurz

     

    We’ve temporarily solved the issue by wrapping the HTML5/JavaScript code in an ASP.NET MVC wrapper… so the ASP.NET code authenticates users via WS-FED in OKTA and then the HTML5 code takes over.

     

    However, we’d like to eventually use this HTML5/JavaScript code as a Mobile Application by wrapping it with Cordova and it’s at that point that we’re not sure the best approach to integrate with OKTA since we won’t have the ASP.NET wrapper there.

     

    We’re open to any suggestions and I’ve cc’d in one of the main developers on that project.

     

    Patrick Kurz, Solution Architect
    Expand Post
This question is closed.
Loading
What is the suggested way to authenticate users through a pure HTML5/Javascript client application?