Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug on EXODkimSigningConfig (wrong Key size value) #4805

Closed
YenNantes opened this issue Jun 27, 2024 · 0 comments · Fixed by #4807 or #4842
Closed

Bug on EXODkimSigningConfig (wrong Key size value) #4805

YenNantes opened this issue Jun 27, 2024 · 0 comments · Fixed by #4807 or #4842
Assignees
Labels
Bug Something isn't working Exchange Online

Comments

@YenNantes
Copy link

Description of the issue

EXODkimSigningConfig resource report a wrong Keysize value.
The value is always 1024 but when checking the real value on the tenant using Get-DkimSigningConfig, the value is 2048.
Additionnaly the Keysize attribute does not exists for this object.
The right attributes are now Selector1KeySize and Selector2KeySize

I guess that the attribute/value is hardcoded on the resource as the keysize was 1024 in the past.

Microsoft 365 DSC Version

1.24.626.1

Which workloads are affected

Exchange Online

The DSC configuration

EXODkimSigningConfig "EXODkimSigningConfig-eurofinstest15.eurofins-test.com"
        {
            BodyCanonicalization   = "Relaxed";
            Enabled                = $True;
            Ensure                 = "Present";
            HeaderCanonicalization = "Relaxed";
            Identity               = "xxxxxxx";
            KeySize                = 1024;
        }

Verbose logs showing the problem

PS C:\script\ExchangeOnlineConfig> Get-DkimSigningConfig |select select*

Selector1KeySize           : 2048
Selector2KeySize           : 2048

Environment Information + PowerShell Version

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Exchange Online
Projects
None yet
2 participants