High value on AUTH_HASH_TTL in zoneminder gives zmninja auth timeout problems

[xztraz]

example: Android 8.0.0
zmNinja 1.3.087
Centos 7
ZoneMinder v1.34.0

In Zoneminder config
setting AUTH_HASH_TTL to 200 works fine
setting AUTH_HASH_TTL to 2000000 don't work.

zmninja says auth is being renewed. then reports 1***9999 something minutes left on auth. then repeats again and again.. app is bombarded with auth ok messages.

[welcome]

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you follow the issue template or I may not respond.

[pliablepixels]

Note that in ZM AUTH_HASH_TTL is hours, so setting it to 2000000 means 7200000000 seconds. However, what you reported, if correct is a bug. Thanks.

[pliablepixels]

I am not seeing this issue.

• I set AUTH_HASH_TTL to 2000000 (hrs) in ZM
• Validated that the API returns the correct seconds:

{"access_token":"ey<deleted>Q1I","access_token_expires":7200000000,"refresh_token":"eyJ<deletedB4E","refresh_token_expires":86400,"credentials":"auth=2be<deleted>,"append_password":0,"version":"1.33.16","apiversion":"2.0"}

Then ran zmNinja and it computed correctly:

Jan 28, 2020 09:33:40 AM Inside _doLogin()
filelogger.min.js:6 Jan 28, 2020 09:33:40 AM No need for re-captcha checks with tokens
filelogger.min.js:6 Jan 28, 2020 09:33:40 AM Resetting zmCookie...
filelogger.min.js:6 Jan 28, 2020 09:33:40 AM Detected token login supported
filelogger.min.js:6 Jan 28, 2020 09:33:40 AM Access token still has 119999999 minutes left, using it
filelogger.min.js:6 Jan 28, 2020 09:33:40 AM ----> Setting token re-login after 7199999940 seconds
filelogger.min.js:6 Jan 28, 2020 09:33:40 AM auth-success broadcast:Successful

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.