There is no good examples nor parameter descriptions in help. When I do the following, the user does not have Integrated Security turned on:
$RdmUserName = 'domain\user'
$UserProps = @{
Login = $RdmUserName
IntegratedSecurity = $true
SkipCreateSQLServerLogin = $true
}
$RdmUser = New-RdmUser @UserProps
$RdmUser.UserType = 'User'
Set-RdmUser -User $RdmUserBefore using Set-RdmUser the user's IntegratedSecurity property is $true. After Set-RdmUser, the same property is $false. Also, the created user's CustomSecurity property doesn't have IntegratedSecurity mentioned (as other users created through GUI have).
The data source used, is SQL Server data source.
Meelis
Hi Meelis,
I'll look into it right away and let you know what I can find.
Regards
Jonathan Lafontaine
Hi,
As far as I can see, for IntegratedSecurity to be taken into account, SkipCreateSQLServerLogin must be $false.
Jonathan Lafontaine
Hi,
As far as I can see, for IntegratedSecurity to be taken into account, SkipCreateSQLServerLogin must be $false.
still the same result.
The SQL database is created as Contained database, this is why I added -SkipCreateSQLServerLogin
How do you validate the user has or not Integrated Security turned on so I can do the same on my side.
Jonathan Lafontaine
How do you validate the user has or not Integrated Security turned on so I can do the same on my side.
By looking at it in RDM GUI. Users with Integrated Security have the button that allowed to choose user account from Active Directory present. Users created by script don't have that button.
Additionally, users with Integrated Security turned on using GUI, have CustomSecurity attribute with similar XML content inside:
<?xml version="1.0"?> <CustomSecurity> <IntegratedSecurity>true</IntegratedSecurity> </CustomSecurity>
Users created by script don't have that.
I tested with added user and the user was able to access data source (using integrated security). That raises the question, how can I later detect that user was created with Integrated Security turned on? Or is it important at all?
Meelis
Hi,
We are able to reproduce the bug on our side. It will be fixed on the next release. For the moment, the IntegratedSecurity parameter is not working.
Which version of module it would be? I currently have 2022.2.3.0 and everything seems the same.
That would be 2022.3 that is scheduled to release today.
Jonathan Lafontaine