You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When working with multiple Keepass databases across different Google accounts, the plugin doesn't seem to adhere to the configured settings. I was surprised to find that Database B on Google A Drive. It's possible that the plugin is using the incorrect token. I'm uncertain why this issue occurs, but I've observed multiple instances where different databases are linked to the wrong accounts. These databases are utilized by various individuals and across different computers to sync with their respective accounts. Each database has a unique Google account configured and the first time Sync was made for this uniuque Account with the correct credentials. Despite Database B being configured for Google Account B, it appears to sync with Account A. I would recommend implementing a check before syncing the database to ensure that the account configured in the settings matches the token being used.
To Reproduce
Not possible to reproduce because I can not define, what is triggering the problem. But I have seen more then 3 different Databases in my own Google Account, which are not configured in the Sync settings. I can say that these Databases was opened at the same time (parallel) in Keepass Application.
Expected behavior
Sync Database A to Google Account A
Sync Database B to Google Account B
Check Accountname before Sync!
Screenshots
Please provide the following information:
OS, Win11 Version 10.0.22631 Build 22631
Firefox 125
Plugin Version [4.1.0]
KeePass Version [2.56] Portable
The text was updated successfully, but these errors were encountered:
Describe the bug
When working with multiple Keepass databases across different Google accounts, the plugin doesn't seem to adhere to the configured settings. I was surprised to find that Database B on Google A Drive. It's possible that the plugin is using the incorrect token. I'm uncertain why this issue occurs, but I've observed multiple instances where different databases are linked to the wrong accounts. These databases are utilized by various individuals and across different computers to sync with their respective accounts. Each database has a unique Google account configured and the first time Sync was made for this uniuque Account with the correct credentials. Despite Database B being configured for Google Account B, it appears to sync with Account A. I would recommend implementing a check before syncing the database to ensure that the account configured in the settings matches the token being used.
To Reproduce
Not possible to reproduce because I can not define, what is triggering the problem. But I have seen more then 3 different Databases in my own Google Account, which are not configured in the Sync settings. I can say that these Databases was opened at the same time (parallel) in Keepass Application.
Expected behavior
Sync Database A to Google Account A
Sync Database B to Google Account B
Check Accountname before Sync!
Screenshots
![grafik](https://private-user-images.githubusercontent.com/45741845/328115590-57f25a15-2065-4e89-9142-54c24d388737.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk0NjYxNDEsIm5iZiI6MTcxOTQ2NTg0MSwicGF0aCI6Ii80NTc0MTg0NS8zMjgxMTU1OTAtNTdmMjVhMTUtMjA2NS00ZTg5LTkxNDItNTRjMjRkMzg4NzM3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MjclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjI3VDA1MjQwMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWYxODAyODg5MTZlYzk0MzZmYjM4NDUwYTllYWNkZWU5NzFhMzVlZjRlODQwNjczNjc3ZmQ5ZTEyMzFjNDNlODImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.9elPt0ne2DAJEVoDSGnqwavaEuRWQPFeLUzEfy61A5I)
Please provide the following information:
The text was updated successfully, but these errors were encountered: