I finally found a solution: Go to your Google API Console (https://console.cloud.google.com/), create a new project ("KeePass" for example), add the Google Drive API and add an OAuth 2.0-Client-ID. You get a client-id and client-key. Now open the "Google Sync Plugin Configuration" in KeePass and check "Custom OAuth 2.0 Credentials". Enter your client-id and client-password. I think it may be a bit difficult for many people, so write me if you don't know how to do this. I'm short of time but will try to help you. Worked with Google Sync Plugin 3.0.1.0 in KeePass 2.44 (Windows 10).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I do not seem to be able submit the OAuth consent screen for verification
(Greyed out). I think this may be because it may want authorized domains,
privacy link, etc which I do not have any such info,
I do not want to chew up any OAuth logins so I will wait to hear back from
you.
I appreciate any cycles you can assist me with in getting this working.
I finally found a solution: Go to your Google API Console ( https://console.cloud.google.com/), create a new project ("KeePass" for
example), add the Google Drive API and add an OAuth 2.0-Client-ID. You get
a client-id and client-key. Now open the "Google Sync Plugin Configuration"
in KeePass and check "Custom OAuth 2.0 Credentials". Enter your client-id
and client-password. I think it may be a bit difficult for many people, so
write me if you don't know how to do this. I'm short of time but will try
to help you. Worked with Google Sync Plugin 3.0.1.0 in KeePass 2.44
(Windows 10).
I do not seem to be able submit the OAuth consent screen for verification
(Greyed out). I think this may be because it may want authorized domains,
privacy link, etc which I do not have any such info,
I do not want to chew up any OAuth logins so I will wait to hear back from
you.
I appreciate any cycles you can assist me with in getting this working.
-John
On Wed, Feb 5, 2020 at 9:55 AM "Andreas Löwer"
originalandy@users.sourceforge.net wrote:
I finally found a solution: Go to your Google API Console ( https://console.cloud.google.com/), create a new project ("KeePass" for
example), add the Google Drive API and add an OAuth 2.0-Client-ID. You get
a client-id and client-key. Now open the "Google Sync Plugin Configuration"
in KeePass and check "Custom OAuth 2.0 Credentials". Enter your client-id
and client-password. I think it may be a bit difficult for many people, so
write me if you don't know how to do this. I'm short of time but will try
to help you. Worked with Google Sync Plugin 3.0.1.0 in KeePass 2.44
(Windows 10).
I created a Google Drive Sheets file and put the Shareable Link into the
OAuth configuration.
This now allowed me to submit for verification :-)
I set the scope to - ../auth/drive.file but I am unsure as to how to link
Keepass to the appropriate password database, any guidance as to how to
limit only to the keepass password files?
I do not seem to be able submit the OAuth consent screen for verification
(Greyed out). I think this may be because it may want authorized domains,
privacy link, etc which I do not have any such info,
I do not want to chew up any OAuth logins so I will wait to hear back from
you.
I appreciate any cycles you can assist me with in getting this working.
-John
On Wed, Feb 5, 2020 at 9:55 AM "Andreas Löwer"
originalandy@users.sourceforge.net wrote:
I finally found a solution: Go to your Google API Console ( https://console.cloud.google.com/), create a new project ("KeePass" for
example), add the Google Drive API and add an OAuth 2.0-Client-ID. You get
a client-id and client-key. Now open the "Google Sync Plugin Configuration"
in KeePass and check "Custom OAuth 2.0 Credentials". Enter your client-id
and client-password. I think it may be a bit difficult for many people, so
write me if you don't know how to do this. I'm short of time but will try
to help you. Worked with Google Sync Plugin 3.0.1.0 in KeePass 2.44
(Windows 10).
I can not put any files on the program files directory on my windows 10 system.
Is there any alternate location/method for pointing keepass2 for the GoogleSyncPlugin.plgx file and storing in a directory in my user directory?
Use the portable app. Then you can put it wherever you want
that works in most cases
my problem is that I can't install new programs.
the plugin doesn't execute itself so won't be blocked.
is the some place that it can search in my appdata folder or other user
folder for the plugin?
Thanx
On Mon., Feb. 3, 2020, 8:00 p.m. Dan E, dane7@users.sourceforge.net wrote:
I finally found a solution: Go to your Google API Console (https://console.cloud.google.com/), create a new project ("KeePass" for example), add the Google Drive API and add an OAuth 2.0-Client-ID. You get a client-id and client-key. Now open the "Google Sync Plugin Configuration" in KeePass and check "Custom OAuth 2.0 Credentials". Enter your client-id and client-password. I think it may be a bit difficult for many people, so write me if you don't know how to do this. I'm short of time but will try to help you. Worked with Google Sync Plugin 3.0.1.0 in KeePass 2.44 (Windows 10).
Hey Andy,
I tried to reply directly but it bounced back.
Thank you so much for your suggestion.
I had tried this before but never got it working.
This is my new take at it :-)
I logged into https://console.cloud.google.com/
https://console.cloud.google.com/getting-started?pli=1 the created a
project named keepass20
I set the OAuth consent screen user type to External and entered an
application name of keepass20 and pressed save
I then went to the Credentials service and created OAuth Client ID
I selected an application type of other and name of keepass20 and pressed
create
This then gave me a
Does this look right so far?
How does the OAuth consent screen get published?
OAuth is limited to 100 sensitive scope logins
https://developers.google.com/identity/protocols/googlescopes until the OAuth
consent screen
https://console.cloud.google.com/apis/credentials/consent?project=keepass20-267418&supportedpurview=project
is
published
I do not seem to be able submit the OAuth consent screen for verification
(Greyed out). I think this may be because it may want authorized domains,
privacy link, etc which I do not have any such info,
I do not want to chew up any OAuth logins so I will wait to hear back from
you.
I appreciate any cycles you can assist me with in getting this working.
-John
On Wed, Feb 5, 2020 at 9:55 AM "Andreas Löwer" originalandy@users.sourceforge.net wrote:
Is there any method to use appdata for the googlesync plugin on windows 10?
On the Keepass Help Centre it shows:
Local User Application Data C:\Users*User Name*
\AppData\Roaming\KeePass\KeePass.config.xml
I tried to install the googlesync plugin into: C:\Users\User
Name\AppData\Roaming\KeePass
I also tried to instgall the plugin into: C:\Users\User
Name\AppData\Local\VirtualStore\Program Files (x86)\KeePass2x\Plugins
When I check for plug ins, I do not seem to find the plugin
Any ideas as to whether or not this is even possible or if I am missing
something simple?
I think my issue at this point is defining the OAuth consent screen.
Two items that I do not know how to define because it requires an active
web page to be configured are:
A homepage URL is required for publishing.
A privacy policy URL is required for publishing.
I think that the scope section would also be prudent to protect misuse of
this api but I am not sure how to lock it down to KeePass2
does this make sense?
https://www.googleapis.com/auth/drive.file
(View and manage Google Drive files and folders that you have opened or
created with this app)
Thanks in advance for any ideas :-)
On Thu, Feb 6, 2020 at 1:20 PM xqxq xq1xq1@users.sourceforge.net wrote:
Okay so trying to move forward on my own.
I created a Google Drive Sheets file and put the Shareable Link into the
OAuth configuration.
This now allowed me to submit for verification :-)
I set the scope to - ../auth/drive.file but I am unsure as to how to link
Keepass to the appropriate password database, any guidance as to how to
limit only to the keepass password files?
On Sun, Feb 9, 2020 at 6:56 PM xqxq xq1xq1@users.sourceforge.net wrote: