Authentication type in User Management
I cannot find documentation on how the displayed value for Authentication type is determined. Pulling an object in powershell, I see that are is a UserType property that I can't find any documentation on, as well.
We have several users that use Integrated Security, yet the drop down that is on users I just imported with powershell is not available and the type shows Database. I've even tried deleting the users and recreating them to see if there was any change with no result.
Can someone clarify/document the purpose of the dropdown and why some of the entries show Database instead of Domain when there is Integrated Security on the users? Also, is there any documentation on user properties? I would expect that all the properties of all objects that can be manipulated in Powershell were documented somewhere and perhaps are not published.
Thanks,
Lenard
All Comments (6)
Hello,
What type of Data Source are you using?
If it is a SQL database, because it is the database itself that take cares of the authentication, all accounts authentication type must be set as Database even those created with integrated security. For domain users, the SQL Server ask the domain controller if the user account is valid.
The drop down list for the Authentication type is only available if it is not saved properly and allows administrators to correct it.
If some accounts are set with the Domain authentication type in a SQL Data Source, you just have to set it as Database authentication type.
Best regards,
Érica Poirier
MSSQL Server
Every user I created with Powershell does this while using -IntegratedSecurity and -CreateSQLServerLogin.
Going back to the UserType property, watching the changes, it looks like this is where the choice is defined. Is it safe to simply change the value with Set-RDMUser?
Hello,
It is impossible to alter this property from PowerShell because it is protected and only available as a read only property.
If you want to modify the Authentication type for many users at the same time, select them all and click on the Batch edit button on the User Management dialog. 
On the Batch edit dialog, check the second Override checkbox and select the Database Authentication type and click on OK.
Best regards,
Érica Poirier
Thanks for that.
So, this is a bug then with users created from Powershell, as they create set as Database from the GUI?
Hello,
I have been able to reproduce your issue in PowerShell.
A ticket has been sent to our engineering department.
Best regards,
Érica Poirier
Thanks Erica