You are viewing limited content. For full access, please sign in.

Question

Question

Laserfiche IOS App times out while filling out forms.

asked on June 15 Show version history

Hello,

I am currently having a major issue with the legacy Laserfiche mobile application.

A bit of context:

A few months ago, iOS 26 was released. At the time, we were using Windows Authentication to sign users into the Laserfiche mobile app. After the iOS update, Windows Authentication stopped working for the app.

Since then, we have been using Laserfiche sign-in for mobile users and SSO/SAML for desktop users.

While users are now able to sign in, they are running into an idle timeout issue that was not occurring before. Sometimes this is only a minor inconvenience, but in other cases a user may be filling out a long or complex form, and when they submit it, they are redirected to the sign-in page. This causes all of their entered form data to be lost.

To disable Windows Authentication, the only change we made was unchecking the Windows Authentication option in the STS configuration.

My questions are:

  1. Is there an idle timeout setting specific to Laserfiche sign-in, STS, or the legacy mobile app that could be causing this?

  2. Is there a recommended configuration for mobile users when Windows Authentication is disabled?

  3. Is there a way to prevent users from losing form data when their session expires?

Any guidance would be greatly appreciated.

0 0

Replies

replied on June 15
0 0
replied on June 15 Show version history

The mobile configuration is currently set to 10,000 minutes for automatic sign out. As far as I can tell that was the fix for your situation.

I would like to clarify, while this is a major issue for us due to the Mobile App signing out, if Forms is left idle in the web client it will also time out and return to the sign-in page.

STS session timeout is set to 1440.

 

Currently I am in a rabbit-hole of IIS app pool idle timeout settings. That has not yet been affective.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.