Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server credentials always showing upon database opening from KeeAutoExec #387

Open
N247S opened this issue Oct 16, 2023 · 1 comment
Open

Comments

@N247S
Copy link

N247S commented Oct 16, 2023

Goodday,

Not sure where to find any support for KeeAutoExec, as I feel like this is more a problem for that plugin.
But since it is related to a KeeAnywhere-database/url I thought maybe someone here knows what I am overlooking?

I am trying to sync a database from/to dropbox, which works well, but as soon as a second file is openend (through the KeeAutoExec), it asks for server credentials, eventhough those are not required?
If I either enter a correct username/password combo or nothing at all, it opens the database. But as soon as I fill in half or something incorrect, it doesn't work.

I tried several options to see what works for 'not showing' this credentials window.

  • If I set the option 'Remember user name and password' without any credentials, it will still ask for credentials upon database activation.
  • If I set the option 'Remember user name and password' with credentials, it tries it with credentials and fails because it is not the 'master password'? Which seems odd, because saving username and credentials should only be regarding the server-settings? After either clicking 'continue' or 'change server-credentials' it will open the database file, but only THAT database-file (so it will act as if the database-file was opened on its own instead of a chain from KeeAutoExec).

I tried finding any documentation on the KeeAutoExec to see if it can be configured, but couldn't find anything, apart from this post on superuser.com describing things are expected to break when databases are openend from commandline. I am not sure if this would give option for KeeAnywhere for a workaround? but it seems like in the background it uses simular mechanisms for opening a database with KeeAutoExec creating this inconvenience.

Would love to hear any input to this

@Kyrodan
Copy link
Owner

Kyrodan commented Apr 5, 2024

Maybe it's the same reason like in #66?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants