dsccommunity / dsccommunity/ComputerManagementDsc
ScheduleTask doesn't work properly with domain credentials
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 338
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
Description
If you use domain credentials with login like domain\username or username@domain, Test-DSCConfiguration will say that this resources not in desired state, because, as I understand, $task.Principal.UserId which is used in Get-DSCConfiguration give you only username, without any domain specification.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the ScheduleTask resource through Test-DSCConfiguration and Get-DSCConfiguration, focusing on how $task.Principal.UserId is compared. Reproduce the mismatch with domain\username and username@domain credentials, then confirm that the resource reports the desired state correctly for both forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- authentication, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100