LongRange Developer Forum

Hi,

We want to use Active Directory Federation Services to do our LongRange app authentication. Unfortunately the way Active Directory Federation services works is that it redirects the webpage to the third party login form and returns a cookie and token on successful authentication.
Is it possible to read the cookie or some data (i.e. HTML, javascript variable) inside the web view from the LongRange container? Also, once we have read from the web view control is it possible to load another LongRange form based on the results of the content inside the web view?

With the current version of LongRange, it is not possible to do exactly what you want.

The problem: there is no way for the JavaScript to get LongRange to perform a submit and move on to the next screen.

One way to solve this problem as an interim solution is to have a button that user would have to manually interact with - the handler for this button will then do a form submit which moves LongRange to the next screen after successful login.

What sort of screen is this? Is it just a webview, or native LongRange forms?

The application is a native LongRange form. The web view control is only for login so that the user can enter their credentials and authenticate against a third party Active Directory Federated Service. We want the native LongRange form to be able to interact with the web view control so that we know if the user has logged in successfully and forward them to the next native LongRange form.

Adding to Siyaman's post, we would realistically also want to be able to use Javascript to take information from the webview itself and write it to the LongRange container to be passed to the next Native LongRange form when triggered. The idea is to be able to farm out the authentication process to any web based authentication service.

I may have answered my own question about this. I was able to set the document.location.href using javascript in a webview inside a Long Range form and use the longrange:// protocal to call the external invocation form to navigate to another native LR form. This also gives the benefit of being able to pass parameters through the URL string.