Shouldn't xService SET the credential whenever it SETs?

[Jaykul]

Problem description

I can't find a way to rotate service credentials using xService

Suggested solution

It seems to me that the logic for credentials in xService should follow the pattern in xScheduledTask: if the credential is provided, set the credential. Presumably the Set only runs when Test fails, so it wouldn't result in restarting the service over and over or anything like that...

Alternatively, the resource needs to cache a hash for the username + password and update them if the hash changes. People can't change the username of their credential every time they want to change the password!

Operating system the target node is running

Windows Server 2019

PowerShell version and build the target node is running

PS 5.1

xPSDesiredStateConfiguration version

Name                         Version
----                         -------
xPSDesiredStateConfiguration 9.1.0
xPSDesiredStateConfiguration 5.1.0.0

[PlagueHO]

I think we might have to use the alternate approach because I think (and need to confirm this) the Test for the Credential property, will just look at the username. Therefore, if we just allowed Set to fire whenever Credential is configured then I presume Set will run every execution - which even if it doesn't restart the service will report that the resource is never in state. Apologies if I'm misunderstanding.

I think ScheduledTask works that way too (just compares the username and if that is different, changes the password) - again, I could be wrong (a while since I've worked on those).

Hashing the password would work I think - @johlju - have you seen us use a similar approach elsewhere? How do you manage this sort of thing in SQLServerDsc?