Offline SSO Should Use the Client Timeout Window Under Account Settings

We have over a thousand users and we'd like to use SSO so we can manage passwords. We also have users that go into remote areas with no cell coverage. Using the regular GoCanvas username and password (non-SSO) login, users can login and sync and can go offline and still submit. When using SSO, it requires to the user to always have an internet connection because it'll prompt the user again for a username and password even if they recently entered them. We need the app to remember that the user signed in successfully and not prompt again for 24 hours. One of the main selling points for your app is its offline ability, but when using SSO it does not work offline. Can it recognize that someone logged in within the client timeout window?

Steps to reproduce the problem:

non-SSO Test (iOS):
1. Sign in using GoCanvas username and password
2. Kill app (or switch to another app for a few hours so GoCanvas gets deallocated from memory)
3. Enable airplane mode
4. Open GoCanvas
Results (All Good):
Everything seems to work as usual and it logs in using the cached GoCanvas username and password that were last used.
I can submit using the apps and it saves the submissions until I connect to the Internet later.

SSO Test (iOS):
1. Sign in using SSO
2. Kill app (or switch to another app for a few hours so GoCanvas gets deallocated from memory)
3. Enable airplane mode
4. Open GoCanvas
Results (All Bad):
Cannot login to app because no network connection. Does not cache the previous SSO authentication or token. Users in the field without Internet connection are not able to use the app to collect data.

Chris Crowley

September 13, 2021 14:20

Any word on getting SSO working correctly? We would love to switch our whole company over to SSO, but we can't currently until this problem is fixed. We have employees that go to remote locations without network connectivity and they need GoCanvas to work in order to do their job.

GoCanvas Community Manager

September 17, 2021 14:17

Hi Chris,

Unfortunately, I don't believe this is a problem that we can fix because of the nature of SSO. Because it requires an active internet connection to ping tokens back and forth to keep the user logged in, it's not compatible with a fully offline solution. The Help Center Article that is dedicated to SSO explains it a little better than I am able to. My apologies that I don't have a better answer for you!

Comments