File: content/manuals/enterprise/security/enforce-sign-in/methods.md
Issue
The Mac configuration profile example contains two PayloadUUID fields with different values, but the replacement instructions are ambiguous about how to handle them.
The example shows:
<key>PayloadUUID</key>
<string>eed295b0-a650-40b0-9dda-90efb12be3c7</string>
...
<key>PayloadUUID</key>
<string>0deedb64-7dc9-46e5-b6bf-69d64a9561ce</string>
The instructions state:
Replace PayloadUUID with a randomly generated UUID
This is ambiguous because:
- There are two PayloadUUID fields (one in the inner payload, one in the outer configuration)
- The instruction uses singular "UUID" but there are two UUIDs in the example
- It's unclear whether both should be replaced or just one
- It's unclear whether they should be different UUIDs (as shown in the example) or the same
Why this matters
Administrators following these instructions might:
- Replace only one UUID and leave the other as the example value
- Use the same UUID for both fields when they should be different
- Be unsure whether the configuration is correct
This could lead to configuration profile deployment failures or conflicts if multiple administrators use the same example UUIDs.
Suggested fix
Clarify the instructions to explicitly address both UUIDs:
Replace placeholders:
- Change
com.yourcompany.docker.config to your company identifier
- Replace
Your Company Name with your organization name
- Replace both
PayloadUUID values with randomly generated UUIDs (each should be unique)
- Update the
allowedOrgs value with your organization names (separated by semicolons)
- Replace
company.proxy:port with http/https proxy server host (or IP address) and port
Found by nightly documentation quality scanner
File:
content/manuals/enterprise/security/enforce-sign-in/methods.mdIssue
The Mac configuration profile example contains two
PayloadUUIDfields with different values, but the replacement instructions are ambiguous about how to handle them.The example shows:
The instructions state:
This is ambiguous because:
Why this matters
Administrators following these instructions might:
This could lead to configuration profile deployment failures or conflicts if multiple administrators use the same example UUIDs.
Suggested fix
Clarify the instructions to explicitly address both UUIDs:
Found by nightly documentation quality scanner