- This topic has 19 replies, 4 voices, and was last updated 3 years, 6 months ago by
.
-
Posts
-
I have been able to get it working by creating a new Group and token, the original groups and tokens would not work with 8.6.511, possibly other firmware too since the upgrade to WMS 3.
The clients are definitely checking in new and old groups but the original groups are not running the “advanced options” as you could see in the logs.
Its is currently working fine now, I have created new tokens for the original groups and will perform more testing etc.
Thank you for your help, much appreciated David.
Question – is this post just about suppressing the alert message on the login screen or how to enable secure communication?
I need to do the later but it does not work so far.
SecurityPolicy=warning SecuredNetworkProtocol=Yes TLSMinVersion=1 TLSMaxVersion=3
Thanks, Steve
Hi Steve
Our original issue was as you mentioned trying to suppressing the alert but found that after upgrading WMS from 2.1 to 3.0 we were required to change the token length and special key requirments. Once this was performed we have not experienced any communications issues and alerts.
Regards
David.
Hi David,
many thanks for the reply.
I’ll try to fix the message with your given help
regards,
Steve
Hi David,
we still encounter the same problem.
Our WMS update path was from 1.4 -> 2.0 -> 2.1 -> 3.0 on a single day.
Since ThinOS 8.5+ we have the “security alert” message at the logon screen.
Just by altering the group token did not help here.
Info: Connection via WMS Cloud and UAG
regads,
Steve
- You must be logged in to reply to this topic.