Hi. I’ve been using the Sign-In Widget for the past 5+ years without issue. Recently, my office upgraded the browser we use internally, and my webapp is no longer recognizing credentials or cookies. If I sign in using the same webapp and then navigate to a different webapp that uses the same SSO credentials, I’m already logged in, so I know the Sign-In Widget is doing its job. I’m thinking it’s likely the code I’m using to validate authenticated users. Can anyone tell me what I might need to change to get it to recognize credentials? Or rather, what’s the easiest way to validate the cookies/tokens of logged in users?
Using Sign-In Widget v 2.16.0 (yes, I know it’s old, but when I try to update the widget I can’t get it to work).
Browser we’re using is Citrix Enterprise Browser (Latest version. Last version worked).
This is the beginning of the code I’m using:
<script type='text/javascript'>
var oktaSignIn = new OktaSignIn({
baseUrl: 'https://sso.xxxxx.com'
});
oktaSignIn.session.get(function (res) {
// If we get here, the user is already signed in.
if (res.status === 'ACTIVE') {
If I go to xxxxx.com it shows me all of my login info with a status of ‘active’.
Just not sure why this browser update (chromium-based browser) isn’t recognizing the credentials with the code I’m using. Other internal apps work. I think I might just not be validating the credentials correctly and I don’t know how to solve it. Wondering if anyone has any knowledge about anything that may have changed in Chromium-based browsers (works in Google Chrome though).
I tried updating the widget version last week without success.