Hello everyone! I recently upgraded an app from 9.24.6 to 9.24.31. After the upgrade I noticed some odd behavior when trying to login with a local account. When trying to login via SSO (we use SAML) there is no issue, you're redirected to our IdP and then back into the app. But when trying to go to the local login page (which is just a version of /login.html without the /SSO/ redirect) and you click the 'Sign In' button you get redirected to the index3.html page, which is expected, but then immediately redirected to /login.html which has an /SSO/ redirect so it logs you in via SSO even when trying to login as MxAdmin. index3.html has that snippet of code that checks for originURI cookie and if it doesn't exist, then sets it to login.html, but I don't know why it's immediately redirecting to that cookie value as it wasn't doing that before the upgrade (nor is it doing it in any other app on this same version). Anyone have any insight on this or what exactly originURI is used for if anything besides after logging out? EDIT: I was actually able to resolve the issue... after stepping through the role based homepage microflow set up in navigation, I found there was an error ocurring when trying to filter an empty list with parseInteger. A simple empty check to avoid this action resolved the error and therefore the application didn't redirect to the originURI value. I'm not sure why this only happened after upgrade but if anyone has a similar issue I would check any custom login logic you have. Thank you!
asked
Ben Brennan
1 answers
0
Hi Ben,
we too face this same kind of issues, we tried lower the SAML Module version and it worked well, you'll try this ben