Skip to content

DUSW: Update user-scoped profile verification logic #35504

@MagnusHJensen

Description

@MagnusHJensen

Related user story

#34243

Task

This also includes non SCEP profiles that is strictly user scoped.

  1. If a User scoped SCEP profile comes through as successful in MDM response, mark as Verified (skip Verifying, and do not do any OSQuery validations).
  2. If a ONLY user-scoped regular profile comes through as successful in MDM response, mark it as Verified (skip Verifying, and don't do any OSQuery validations).
  3. If a mix of device-scoped, and user-scoped regular profile comes through, set it to Verifying on successful MDM response (current behavior), but do not do any OSQuery validation for the User-scoped LocURI's, only for the device-scoped.

Condition of satisfaction

A profile that only contains user-scoped LocURI's (SCEP or non-SCEP), moves toVerified once a successful MDM response comes through, and does not get validated when OSQuery reports back.
A mixed profile keeps the current flow, except user-scoped LocURI's are not validated in the OSQuery report.

Metadata

Metadata

Assignees

Labels

#g-mdmMDM product group~sub-taskA technical sub-task that is part of a story. (Not QA'd. Not estimated.)

Type

No type

Projects

Status

✅ Ready for release

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions