What is the best way to troubleshoot failed user logins?
Hi,
We use DVLS 2023.3.14.0.
We use the login via Active Directory accounts.
Single sign-on via the web portal and RDM works without any problems.
We also use login via AD user and password from certain network segments.
Here we sporadically receive the message "Invalid username or password, please verify your credentials" - of course the credentials have been checked. Single sign-on works for the same accounts.
The question now is how we can best troubleshoot the reason for the message?
Best regards
All Comments (7)
Hello,
Thank you for reaching out to us on that matter!
Are you getting the "Invalid username or password" prompt when trying to log in to the Devolutions Server through RDM or when trying to connect to a remote host?
You could also try opening the Profiler in RDM under the Help tab and set it to Debug Only with the debug level set to 106499. You can then send us the profiler trace to service@devolutions.net, and please include the forum URL in your email.
Best regards,
Good Morning,
we are getting the error when trying to log in to DVLS through RDM or when trying to log in directly using the DVLS webinterface.
I have already sent the profiler trace.
Would there also be a way to troubleshoot this directly in DVLS (e.g. what was the reason for the failed login attempt)? So that we can troubleshoot this ourselves in the future?
Best regards
Hello,
You could try enabling the log debug information under Administration > Server Settings > Logging and verify the Data Source Logs under the reports.
Note that we recommend disabling the option afterward since it can create a lot of logs inside the database.
There is also a Login attempt report you can look into.
Best regards,
Hi,
thanks for the hint.
I have enabled log debug information under Administration > Server Settings > Logging and tried to log in via AD username and password (with failed).
The Data Source Logs under the reports where just empty - even if I select all message types.
I can see the login attempt within the report - but only that there was a login attempt - not why it failed...
Are there any other ways for us to find out why the login attempts sporadically fail?
Or did the transmitted trace logs help for an analysis?
Best regards
Hello,
From what we can see from the Profiler trace you sent, we were not able to pinpoint the cause of the issue. I will get back to you in the email you sent in order to maybe get more logging information.
In the meantime, you could try the diagnostic tool under Administration > Server Settings > Authentication > Domain to test the different diagnostic and strategies in order to find the best one for your need. You can edit those strategies under Administration > Server Settings > Authentication > Domain > Advanced Settings.
Best regards,
Hi was this solved?
Upgraded to RDM 2024.2.12 and Server 2024.2.5.0 and we are not able to login anymore.
Hello,
This issue was resolved.
To prevent being locked out of the Devolutions Server after an upgrade or with any issue that might come up with the primary authentication method, we recommend keeping at least one Devolutions Custom User that is set as an administrator. This account will be used as a break glass account. During the installation process of the Devolutions Server, you will be prompted to create that account. This account cannot be created through the database.
Best regards,