I have Keepass2 setup on a Debian machine and have been able to get the Google Sync Plugin to run. I have configured all the necessary credentials and OAuth settings and when I tryed to sync I was getting a request error. My desktop is behind a company firewall that uses a 3rd party url filtering system so on the WIndow's machines we use a .pac file to configure our browsers.
On my Debian machine I have setup an instance of tinyproxy and cloned the .pac file details for the upstream/no upstream definitions
I set the proxy settings in Keypass2 to use my system proxy and I saw the traffic through the proxy and got the error. Because of my job I'm able to bypass the url filters if need be so I next set Keypass proxy to use no proxy settings and I first made sure I could access accounts.google.com directly and could. However when I re-ran Keypass with the proxy settings set to "No Proxy" the plugin still went through my local proxy (system default) which indicates to me that it is not honoring the Keepass2 proxy settings.
My next step was to put the accounts.google.com into my tinyproxy config as a noupstream and when I did that, now the plugin apparently makes a proper connection but it then displays a window titled something like "Google Authorization" but the content of the window is completely blank. If I close that window then I receive an error that authorization failed.
So two issues here, one the plugin appears to ignore the proxy settings for Keepass2 and there is something odd with the input window. My desktop is Debian Jessie running XFCE4 desktop.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Use a Windows machine to do the authorization step. That is only needed once and the obtained authorization key is stored inside the database afterwards. Copy that "authorized" database to your linux machine.
It is known that the authorization window (basically just a browser window) does not work with mono. I know of no case where that has ever worked.
As to the proxy settings: what do you mean by "I re-ran Keypass with the proxy settings set to "No Proxy""?
Is there a KeePass setting I don't know about? Afaik, the proxy handling is done by mono / .net and always uses the system settings (unless you create specific .net .cfg files).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have Keepass2 setup on a Debian machine and have been able to get the Google Sync Plugin to run. I have configured all the necessary credentials and OAuth settings and when I tryed to sync I was getting a request error. My desktop is behind a company firewall that uses a 3rd party url filtering system so on the WIndow's machines we use a .pac file to configure our browsers.
On my Debian machine I have setup an instance of tinyproxy and cloned the .pac file details for the upstream/no upstream definitions
I set the proxy settings in Keypass2 to use my system proxy and I saw the traffic through the proxy and got the error. Because of my job I'm able to bypass the url filters if need be so I next set Keypass proxy to use no proxy settings and I first made sure I could access accounts.google.com directly and could. However when I re-ran Keypass with the proxy settings set to "No Proxy" the plugin still went through my local proxy (system default) which indicates to me that it is not honoring the Keepass2 proxy settings.
My next step was to put the accounts.google.com into my tinyproxy config as a noupstream and when I did that, now the plugin apparently makes a proper connection but it then displays a window titled something like "Google Authorization" but the content of the window is completely blank. If I close that window then I receive an error that authorization failed.
So two issues here, one the plugin appears to ignore the proxy settings for Keepass2 and there is something odd with the input window. My desktop is Debian Jessie running XFCE4 desktop.
Use a Windows machine to do the authorization step. That is only needed once and the obtained authorization key is stored inside the database afterwards. Copy that "authorized" database to your linux machine.
It is known that the authorization window (basically just a browser window) does not work with mono. I know of no case where that has ever worked.
As to the proxy settings: what do you mean by "I re-ran Keypass with the proxy settings set to "No Proxy""?
Is there a KeePass setting I don't know about? Afaik, the proxy handling is done by mono / .net and always uses the system settings (unless you create specific .net .cfg files).