I finally isolated my AD authentication bug on Linux to Royal TS and Royal TS/X. They both have the same problem. I can connect to my domain joined Linux system fine with the credentials that are stored in Royal TS and Royal TS/X, but it fails when I use the same credentials that are stored in the imported KDBX database.
The credentials look identical in the GUI as the ones that work. I figured this out by attempting to authenticate outside in my terminal and then switching back and testing Royal apps. This took me a couple hours to figure out and I’m sorry quite frustrating.
Hi,
I’m not sure I understand. Is this a feature request or a bug report? If it’s a feature request, what exactly are you asking for? If this is a bug report, can you share more information, try to reproduce it with a dummy KDBX file and submit a ticket with a solid repro case?
Thanks,
Stefan
Where can I submit a bug report? I wasn’t sure where to post this last night so i just ended up here.
If it’s not clear whether it’s a bug or intended behavior, the Questions category would be the right place. You can also report bugs by opening a support ticket.
I’m not sure why it would be intended behavior. Is my description clear? I moved the post to questions.
The credential does not work for AD login from my imported keepass database. The credential does work from the credential that is saved inside the document itself. They look functionally identical in the GUI.
Well, it would be helpful to some more troubleshooting on tour side. Is it related to the password or a character in the password? Is it related to AD or di you see the same issue with a different connection type with the same password?
if you can provide a dummy kdbx file and a connection to test this, would be very helpful.
I’m sorry for accusing Royal TS. I’ve been having a rough week
. I did what you recommended and isolated it to caps lock being used in my username. AD authentication with Linux is tricky. So, it’s all working now. Sorry for the trouble.
That’s great news! Glad the issue has been resolved!
1 Like