Pass-through Login Expiring?
A couple weeks ago we enabled Pass-through Logins and it works, so that in IE or Chrome we can go straight to the dashboard, bypassing the login screen unless we specifically "log out." We're rolling out SDP slowly, only a few IT people using it currently, all Technicians in the system. However, I'm seeing a persisent problem. A tech might go to the site and access all the features with no issues. But after filling out the Incident form, clicking the submit button they are asked to log in again. Even when they do, the form does not get submitted and, in fact, they have to start all over again. It seems like the Javascript for the "Add Request" button just freezes at that point, the button disabled.
This happens to one tech about 25% of the time. A couple others have seen it, but I have not been able to reproduce it myself. We have the helpdesk set up as helpdesk.oursite.local, although it is accessible via heldpesk.oursite.org. One tech noticed the difference and once he started using the .local URL, he hasn't seen the problem. However, users are still seeing this issue even when using .local. One tech now reports that he sees it (he thinks) on his first ticket of the day. It prompts him to log in, he does, then it works fine for the rest of the day, as if there is a cookie or other expiring setting.
I'm wondering if there is anything I should look for, either in the admin settings or maybe in the one technician's system that might be causing an issue.
Our install is Build 9012, will be upgrading to 9013 tonight. And the technicians with the persistent issue use IE (the standard for staff in our office).
This happens to one tech about 25% of the time. A couple others have seen it, but I have not been able to reproduce it myself. We have the helpdesk set up as helpdesk.oursite.local, although it is accessible via heldpesk.oursite.org. One tech noticed the difference and once he started using the .local URL, he hasn't seen the problem. However, users are still seeing this issue even when using .local. One tech now reports that he sees it (he thinks) on his first ticket of the day. It prompts him to log in, he does, then it works fine for the rest of the day, as if there is a cookie or other expiring setting.
I'm wondering if there is anything I should look for, either in the admin settings or maybe in the one technician's system that might be causing an issue.
Our install is Build 9012, will be upgrading to 9013 tonight. And the technicians with the persistent issue use IE (the standard for staff in our office).