So… is the reason I’m not getting a response here because my question is so asinine it is not worthy of a response ? Look, I’m pretty novice, my feelings won’t be hurt if you tell me I’m clueless. Please, I’m really in need of some assist here. @nate.barbettini you helped me come up with this model from a previous response, I’m just in need of this seemingly minor point.
Tom, thanks for the response! Didn’t mean for my comment to come off as if I was complaining. I really was wondering if I was barking up the wrong tree. I’ll give it a try. Thanks again!
I’ve got the authClient.session.exists() in place and I think it works. It just always returns false. So basically, the auth app (which redirects to okta) logs in correctly, and then redirects to QV Auth page which contains the session.exists() check. This is the code that performs the redirect:
public ActionResult Index()
{
// Redirect to QV Auth Page
return Redirect ("http://localhost:8043/");
}
Should I be doing some sort of SetCookieAndRedirect() call? I can’t seem to find this call in the Okta SDK for .NET. Why would simply redirecting not pass along the token?
To further test this out, I’ve created an app where the user authenticates through Okta using the ASP.NET middleware. User logs in and correctly gets redirected back to the app. By the way, this is the demo app provided by your web site.
I have further added the javascript API to the same app and added the code you see below to one of the pages. Basically, user presses a button and I invoke the session.exists() method. This is my test of the javascript API (after user logs in through middleware).
I assumed that once the user successfully authenticated, that a token would be present within the session and that the javascript session.exists() method would return true. However, it only returns false. What am I misunderstanding here?
Here is a link to the page I have added the js api to.