I did not find a better category, but this issue relates to Data Connection Manager and credential setup with key files in a Server and Desktop environment.
Issue: When using key file credentials in DCM a Key File Path needs to be specified. This path cannot be a UNC or Mapped drive, has to be a local drive for Google BigQuery with the latest Simba ODBC driver at least. This prevents centralized credentials management and defeats the purpose of DCM. I understand this might be a driver limitation, however it's still an issue that I think Alteryx could handle.
Suggestion: Since the key file is simple text (JSON) file, it could be embedded (i.e. uploaded via the DCM interface) into the connection itself. That way it can be centrally distributed to the local computers when the DCM connections are synchronized from the server (or vica versa). I would also store them encoded for Information security reasons.
Bonus: Tying into this it would be really good if Alteryx Desktop would automatically sync Server DCM connections when a connection is made to Alteryx server the first time after the software was launched (i.e. opening a Server workflow) to keep it automatically updated.