New Data source in RDM + Launcher - Username cannot be left empty
Hi!
We are using DVLS 2022.1.10, Launcher 2022.1.23, RDM 2022.1.23.
In both Devolutions Launcher and RDM we experience the issue that when we try to add a new (DVLS) datasource we must fill out the username field, but when we do O365 auth fails.
our workaround in RDM at the moment is that we export the data source config (with blank username field) from another installation, and import that.
but this is not working for our Launcher users, meaning that they cannot use Launcher.
Has anyone else experienced this problem?
best wishes,
Andreas
All Comments (5)
Hello,
Are the accounts set as Office 365/Azure AD or Domain in Administration - Users?
Do you have any relevant error messages in the DVLS logs when trying to connect from RDM with the username filed populated?
https://kb.devolutions.net/dvls_viewdatasourcelogs.html
You can also check in Reports - Login attempt report to see if there is anything related to the failed attempts.
Best regards,
Érica Poirier
Hi! Thanks for the quick reply!
The Accounts are Office 365/ Azure AD Accounts in Administration - Users.
I cannot find any relevant error messages in the DVLS logs, apart from entries in the Reports - Login Attempt Listing stating "no access to application" (Kein Zugang zur Anwendung)...
Another issue I noted here is that in most, if not all, log reports, the date column is not filled.... could this be an issue with the german translation we are using?
Best regards,
Andreas
Hello,
Thank you for your feedback.
The dates that aren't displayed isn't related to the German translation and we are aware of this issue.
Regarding your issue, could you please enable the Log4net logging utility and then try again from RDM with the username set? Then please send me the DPS_Main.log file in a private message. Here is the article to enable this tool.
https://kb.devolutions.net/kb_dvls_enabling_log4net_log.html
Best regards,
Érica Poirier
Hello!
We've discovered what the issue was: we tried only using the username, not the UPN name (username@domain.TLD) which was required for O365/Azure Auth by RDM/Launcher
Another issue that occurred was that the license for launcher was somehow unassigned from the user.
After correcting both of these issues creating a datasource now works fine!
Thanks for your help!
best regards,
Andreas
Hello,
Thank you for your feedback and glad you have solved the Launcher and Office365 problems.
Best regards,
Érica Poirier