I’ve opened a KDBX File with the “External Credential Vault” menu inside Royal TS on my windows computer. It’s opening fine after entering my Master Password, but for some reason it doesn’t save the password even though it’s set as “Remember Password for subsequent Documents.” I have to re-enter it every time I open the app. I also need to open my royalserver document as well whenever i open the app.
I use KeePassXC and I created a group inside KeePassXC with KeeShare and am loading up that new database into RoyalTS. Note that this is working fine on the macOS app. RoyalTS/X prompts me for my fingerprint, and it loads just fine every time without having to re-enter my master password for my KDBX file ach time.
My applications document is encrypted and also protected with windows hello.
thanks for the question. Right now, TS doesn’t store the KeePass file password in the credential manager. I will add this option to our todo list and implement the same for TS.
I understand implementing these kinds of changes takes time. However, the current behavior with Royal TS and a synchronized Royal Server document breaks my workflow. I want to keep my credentials secured on my local machine outside of the synchronized document. When I’m on my Windows machine, I am forced into the below workflow:
Open the application.
Wait for the previously connected server session to attempt connection and fail, because the external credential vault is locked and cannot supply the credentials.
Manually open the external credential vault and input the master password.
Manually reconnect to synchronized document.
This introduces significant daily friction. The macOS version seamlessly handles this without major interruption.
I implemented the same behavior as TSX has. So hopefully the new behavior doesn’t break your workflow anymore. Stay tuned for one of the next versions where this has been implemented.
Hello, I updated to the new version of Royal TS/X and I’m still having this same issue where my credential is not being stored and I have to go through that long process. Was this issue addressed in these most recent patches?
I got a new computer so had to reinstall Royal TS/X on my macbook. It looks like I can’t find the keepass database import feature inside Royal TS/X on my mac. I’m using Version 6.4.2 of Royal TS/X. I’ve looked all over the app and can’t find it. What am i missing? I did install this from the homebrew, ‘cask “royal-tsx”.’
I know this links is for the windows version, but I tried looking in similar locations and can’t find it.
See below. You can see there is no option for KeePass…
Thank you, that worked. There was nothing really indicating that this was an option. I just went open document and then clicking on a .kdbx file just works.
Kdbx is a bit special as it actually doesn’t “import” and “convert” the keepass file. It just creates a read-only shim to use within the application. Most users do not want to import the file and save it as a rtsz file, they usually want to keep using keepass.
Any update on getting this working with saving the password in Royal TS so you dont have to keep unlocking the database? This workflow has pushed me to use local RDP and terminal on windows.
Thanks, I actually installed this first thing yesterday morning. I appreciate you working on the problem. The master password now stores in Windows Credential Manager. That part is working.
However, the Windows behavior is still different from the macOS version. On macOS, the .kdbx file persists in the left-hand view between sessions, and the first thing the app does on launch is prompt to unlock it. This allows me to store my Royal Server credentials inside keepass and have them resolve automatically for the next step where you connect to the server and open your document.
On Windows, even with the master password saved, the .kdbx file has to be manually selected from File Explorer each time the app starts. It does not persist in the left-hand view between sessions. The master password fix means I’m no longer prompted for it after selecting the file, but the .kdbx file still isn’t available as a credential source at app launch. So when a Royal Server connection tries to resolve credentials at app start, there’s nothing mounted to resolve against.
I was able to work around this by storing the Royal Server credential in the Application dropdown instead. That works, but it still requires manually selecting the .kdbx file each session. Ideally, you’d want all your credentials stored inside KeePass.
