License Assignment and User Creation
Hello.
Two things to report - one is when we create users via "user management" within an advanced data source (with a license already added to the data source), then select one user and click the "assign license" (ribbon) button at the top, it says "no licenses available" even though there are licenses available. Going to the licenses tab and assigning it from that page works properly.
Also when creating a new custom login user, and then trying to initially connect with that user (with SQL credentials entered for the underlying SQL access), it says invalid login. Looking closer I see a successful authentication at the SQL level (with the underlying SQL user). However I can see in the DB, in the UserAccounts table, the Password field for the new RDM user is NULL which I think is the issue. If I go into the user properties and reset the RDM user's password again , then I am able to login with the user. So it is as if the password is not getting set properly on initial creation.
Both of the above are w/ Azure SQL as the data source and on RDM v2023.1.
Thanks
David Willis
All Comments (5)
Hello,
Do you encounter these same issues when updating your RDM version ?
Note that an RDM version update will also require a database upgrade since you're on an Azure SQL as well as 2023.1. The reason is because you'll also be jumping to a new major version (2023.2).
For more on this and the recommended precautions when performing a database upgrade, please see the following: https://docs.devolutions.net/rdm/windows/installation/database-upgrade/
Best regards,
Hello,
License assignment issue appears to be fixed in v2023.2, which is great!
The NULL password issue, however, remains in v2023.2 (still not able to login w/ a newly-created custom user with the initially-set password).
Thanks
David Willis
Hello,
I'm glad to see one of the issues is resolved, may I ask how you're configuring the passwords for your users when creating their user account ?
Best regards,
I'm just typing in the password in the password field in the form when creating the user (with the user type set to "custom (Devolutions)").
David Willis
Hello,
I just opened an intenral ticket for our developers and and contacted them regarding to see if we can figure out what may be happening and if the password being "NULL" is normal.
I'll update you once I have news from them to share.
Best regards,