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

Question

Question

LF Mobile authentication issues

asked on February 24, 2021

After upgrading to the latest 10.4 version, I have noticed major changes to the mobile app's authentication.  It requires logging in with the domain\username and it times out after a while, requiring that credentials get entered again.  I would like to know if there will be an option in version 11 that allows the user to stay logged in after closing the app AND/OR allows the user to sign in using a pin number, fingerprint, or other method to facilitate quick logins.

Thanks.

 

0 0

Replies

replied on February 26, 2021 Show version history

Hi Mike,

We are working on investigating mobile timeout issues related to SSO login. However, if your environment is non-SSO, or mixed (ex: SSO forms and non-SSO repo), I would suggest you file a support case. Also, currently in the app we already support biometric login for the following cases: non-SSO forms & no repo, no forms & non-SSO repo, and cloud.

0 0
replied on February 26, 2021 Show version history

We have SSO Forms and SSO Repository, connected to Active Directory through LFDS. Our LF server is self-hosted on prem.

0 0
replied on June 24, 2021 Show version history

@████████

Any more updates on this issue?  I tried manually setting the timeout to 5000 minutes but it still times out in the same day of the login.  Please advise.

Note: We have upgraded to version 11 and have not seen any improvement in this area.

 

0 0
replied on June 25, 2021

@████████ There are no updates regarding this at this time.

0 0
replied on June 25, 2021

@████████; thanks for the response.  Please keep us updated on this issue as it is a major cause of user annoyance; we are trying to get more users to buy in to using the mobile app and this issue has been very problematic in that regard.

 

0 0
replied on June 25, 2021

By the way, even when the timeout in minutes option is unchecked, it appears that the user is logged out automatically very quickly; usually about 20 minutes or so.

 

0 0
replied on November 12, 2021

We too are having this issue.  We have an open support case for several months, but still no fix.  It is very frustrating for our users.

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

Sign in to reply to this post.