SqlDatabasePermission: Cannot grant or remove connect permission to the guest user

[imarambiocatan]

I'm probably doing something that i should not. I am dynamically generating a number of mof files based on my current environment to test a few controls with DSCEA but in any case the mof file that gets generated for my server has a section that looks like the following

instance of MSFT_SqlDatabasePermission as $MSFT_SqlDatabasePermission1ref
{
ResourceID = "[SqlDatabasePermission]RevokeGrant_guest_model";
 Permissions = {
    "Connect"
};
 ServerName = "<edited>";
 InstanceName = "MSSQLSERVER";
 Ensure = "Absent";
 SourceInfo = "<edited>";
 Name = "guest";
 ModuleName = "SqlServerDsc";
 PermissionState = "Grant";
 ModuleVersion = "11.2.0.0";
 Database = "model";

 ConfigurationName = "SQL_config";
};

using dscea against my server results in something like

WARNING: PowerShell DSC resource MSFT_SqlDatabasePermission failed to execute Test-TargetResource functionality with error message: Login 'guest' does not exist on SQ
L server 'abbsus201\MSSQLSERVER'.

But it clearly does
PS > ($(Get-SqlInstance -ServerInstance localhost).Databases | where-object { $.name -notin @("master",
"msdb", "tempdb") -and "guest" -in $.users.name }).name
model
ReportServer
ReportServerTempDB
SUSDB

[johlju]

We should be able to grant or revoke connect permission as per Best Practices Recommendations. But because this resource wrongly handles logins (which I think only SqlServerLogin should do), that was raised in issue #848 too. This resource can't handle the guest user because their will never be an accompanying login for that user.

[johlju]

I will label this as a bug and help wanted so that someone in the community can run with this.

[johlju]

Oops, wrongly closed the issue. Sorry about that. Reopened.

[johlju]

This will be fixed in the next release.