User not able to login (SQL Azure database)
One of our users has issue's accessing the RDM database. He had used it before and for some reason all was stopped working (ADAL dll - hell issue).
After long trial and error trying to fix this (install and uninstall components on his pc) it worked on his laptop for other accounts except his own account.
I decided to remove his account from RDM and re-create a new login (same email; same name) in hope that after that all would work again. The account is created however he still cannot login. We checked a manual login to the database (using SQL mgmt) and notices he could not login either. When checking db security he has no user while other have got a useraccount in Azure SQL.
See attachment.
What can we do to solve this issue?
2018-10-29_10h20_14.png
All Comments (9)
Hello Sander,
Before jumping to RDM authentication, I would like to repair the issue with SSMS (SQL mgmt).
Could you try with a standard user if you are able to open SSMS and connect to it. If so, try to create/give access to the user directly from AD Azure portal.
With SSMS what is the error received when you try to connect?
Best regards,
David Grandolfo
We might be experiencing the same issue. At least, we are running the Trial to see if we can get Azure AD authentication to work as this is one of the requirements for us. We created the database and when we try to add a user with the Administration --> User level and give him the account type Azure AD integration the user is not created in the database.
When we then maually create the user in the database he can login, but he has to use the Password option. Seems like for some reason the Azure AD Integration is not creating a user within Azure SQL database.
Hi guys,
I just delete my previous message because we were able to reproduce the issue.
Our internal ticket number is RDMW-1476 .
Best regards,
David Grandolfo
Any update on this matter?
For us this issue is solved by updating to 14.0.4 version. We can now add users through RDM with AzureAD MFA (using MFA) and the users get created in the AzureSQL database as contained users.
For the non-working user we had to delete the user and recreate it.
@Sander,
Have you installed RDM 14.0.4.0?
If you recreate your user with this version, are you able to create it properly? Is he able to connect?
Best regards,
Jeff Dagenais
If you have users already created that don't work, first try the "Fix Login" button (hammer). If that doesn't fix it, you will need to delete the user and re-create it.
Best regards,
Edit: Thanks @Bram van den Kerkhof, you are faster than I was at replying and I didn't see your response.
Stéfane Lavergne
Updated the application - try if it works now => Next issue: clicking on 'Users' give me this error (not that I use a SQL login)
NullReferenceException - Object reference not set to an instance of an object.
at Devolutions.RemoteDesktopManager.Forms.FrmSecurityManagement.ca5160a105ba43735210414e1574f8eb7(UserEntity cf98b881282579a38f0d3820b4755fa4a)
at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
at Devolutions.RemoteDesktopManager.Forms.FrmSecurityManagement.get_FixSqlLoginVisible()
at Devolutions.RemoteDesktopManager.Forms.FrmSecurityManagement.c5d9d4bdfff718a5d7e159ef412d419f4()
at Devolutions.RemoteDesktopManager.Forms.FrmSecurityManagement.c81c347c83082c8f27092d107150085af(Boolean ceb9d2241b042f495f5aa0c7d6093924c, Boolean c440bd4e981f9e5440e1357bea1af9714)
at Devolutions.RemoteDesktopManager.Forms.FrmSecurityManagement.Initialize(ISecurityManager securityManager)
at Devolutions.RemoteDesktopManager.Managers.ActionManager.c708816d1c95767c33a3abe0df3fc19d4(SecurityManagementOpenMode c17de7030565f43077466095dd50c1438)
at Devolutions.RemoteDesktopManager.Managers.MainMenuManager.c395f096672f59ebb8079354f25b9919c(Object c19f185fd70cefc696ba148af1c4faf54, EventArgs cf1018bb83ec7debd818319fd3cb4844e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
Hello,
This error is fixed internally. We are about to release a patch later today.
Regards
David Hervieux