canonical / canonical/authd

Issue: Authd and Intune device settings/compliance

Open
#958 15 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
308
Forks
41
Avg merge
2d 4h
Merged PRs (30d)
58

Description

### Is there an existing issue for this?

- [x] I have searched the existing issues and found none that matched mine

### Describe the issue

Configuring authd initially works as expected with the user onboarding and using a local password

Trying to add in intune compliance checking however results in a failure to update device settings

The local password for the authd user is compliant with the password policy but intune does not seem to read the local password store:

`Jun 10 10:31:48 td-ubutst01 intune-portal[3192]: Non-compliant status indicated by IWS issues=[("Enforce a secure password", "This device must be configured to enforce passwords containing at least 1 digits.", "https://go.microsoft.com/fwlink/?linkid=2210011"), ("Enforce a secure password", "This device must be configured to enforce that passwords contain at least 14 characters.", "https://go.microsoft.com/fwlink/?linkid=2210011"), ("Enforce a secure password", "This device must be configured to enforce passwords containing at least 1 lowercase letters.", "https://go.microsoft.com/fwlink/?linkid=2210011"), ("Enforce a secure password", "This device must be configured to enforce passwords containing at least 1 symbols.", "https://go.microsoft.com/fwlink/?linkid=2210011"), ("Enforce a secure password", "This device must be configured to enforce passwords containing at least 1 uppercase characters.", "https://go.microsoft.com/fwlink/?linkid=2210011")]
`

### Steps to reproduce

_No response_

### System information and logs

_No response_

### Double check your logs

- [x] I have redacted any sensitive information from the logs

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the reported intune-portal log and comparing the configured authd password policy with the compliance checks described. Reproduce the failure with Intune device compliance enabled, then determine whether local password policy state is being exposed correctly. Done means authd device settings update successfully and Intune reports the configured password as compliant.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication, operating-systems, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.