Adding a Person to the Deny Access group in the NAB may change the value for Access for their Device, but does not force a disconnect of the Device from the Traveler server. Why? Also, is there a way to confirm a Wipe request if you’re also disconnecting the Device for security reasons?
Subject: RE: Deny access doesn’t end connection
The Deny checks are made on the HTTP request level, so that is done when the device connects. Any existing connections will already be passed that point.
For the wipe to be executed and also to be confirmed, the device must be able to connect to the server. This is mentioned in the wiki doc too. You can deny access to all connections after the wipe is done, but the device must be able to connect until it completes the wipe. Traveler will not allow it to take other actions while the wipe is pending, but once the wipe is done, it won’t be allowed to do anything (and you can deny total access if you want).