Page 1 of 1
WAPT agent that does not update after upgrading from 1.5 to 1.6
Published: October 26, 2018 - 7:59 PM
by troublestarter
Good evening,
After updating the server from 1.5 to 1.6 and regenerating the agent, the WAPT clients are not updating to 1.6.
They remain on version 1.5 with the status "OK" and reachable as "DISCONNECTED".
How can the WAPT agent be updated automatically? (without using GPO because the PCs are remote)
Regards
Re: WAPT agent not updating after upgrading from 1.5 to 1.6
Published: October 26, 2018 - 9:32 PM
by sfonteneau
Can you add
`allow_unauthenticated_connect = True`
conf/waptserver.ini` while the workstations are being migrated to version 1.6?
Re: WAPT agent not updating after upgrading from 1.5 to 1.6
Published: October 26, 2018 - 11:12 PM
by troublestarter
It seems to be working.
I need to understand where I went wrong. Is there a particular reason?
Should I change the value back to "False"?
Regards
Re: WAPT agent not updating after upgrading from 1.5 to 1.6
Published: October 28, 2018 - 2:45 PM
by sfonteneau
We simply didn't take the time in the 1.5 -> 1.6 upgrade documentation to note certain things:
https://www.wapt.fr/fr/doc/changelog.html#changes
https://www.wapt.fr/fr/doc/Configuratio ... tie-option
We changed the WebSocket authentication method. By default, they are not authenticated if `allow_unauthenticated_registration = True`.
When you are coming from version 1.5, if `allow_unauthenticated_registration = False`, then you must switch `allow_unauthenticated_connect = True` to use WebSockets.
Once all clients are updated, you can switch `allow_unauthenticated_connect = False` again.