Change Details

- Connect to the bidirectional gRPC `MessagesStream` stream with the valid `sessionID` in metadata and send the message to the server with the `NewNotifyToken` field value as a random string. The expected behavior is that the value will be written into the sessions table of the dynamoDB database into the `NotifyToken` field; - Make the `NotifyToken` field empty in a record with your `sessionID` key; - Re-connect to the bidirectional gRPC `MessagesStream`; The expected behavior is your client will receive a [[ https://github.com/CommE2E/comm/blob/50d12886e7e757fdb876a84ddcda9b98382bf460/shared/protos/tunnelbroker.proto#L133 | newNotifyTokenRequired ]] message to require the new token from the device which must be sent as `NewNotifyToken` message and will be handled in the D5534 diff.

TBD- Connect to the bidirectional gRPC `MessagesStream` stream with the valid `sessionID` in metadata and send the message to the server with the `NewNotifyToken` field value as a random string. The expected behavior is that the value will be written into the sessions table of the dynamoDB database into the `NotifyToken` field; - Make the `NotifyToken` field empty in a record with your `sessionID` key; - Re-connect to the bidirectional gRPC `MessagesStream`; The expected behavior is your client will receive a [[ https://github.com/CommE2E/comm/blob/50d12886e7e757fdb876a84ddcda9b98382bf460/shared/protos/tunnelbroker.proto#L133 | newNotifyTokenRequired ]] message to require the new token from the device which must be sent as `NewNotifyToken` message and will be handled in the D5534 diff.