Concurrent Authorization Code Usage Question

We’re in the process of reprovisioning a new server which will have insync-headless running on it and will be configuring it for selective sync to Google Drive using the same setup as the server we’re decommissioning.

My question is, if we’re using the same google account on the new system as on the old one and I go through the auth process as part of the setup of the new server and generate a new code to use will that invalidate the existing server’s authorization and stop it from being able to sync?

Hi @Jeremy_Hulford,

Let me clarify this with our engineers and I’ll update you here!


This won’t invalidate the existing setup as per our Linux team. :slight_smile: