mirror of
https://github.com/apple/device-management.git
synced 2026-08-23 08:47:26 +02:00
Seed6
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
title: Asset:Credential Certificate
|
||||
description: 'A reference to a PKCS #1 or PEM encoded certificate.'
|
||||
description: 'A reference to one PKCS #1 or PEM encoded certificate.'
|
||||
payload:
|
||||
declarationtype: com.apple.asset.credential.certificate
|
||||
supportedOS:
|
||||
@@ -21,10 +21,12 @@ payloadkeys:
|
||||
- application/pkcs1
|
||||
- application/pem
|
||||
presence: required
|
||||
content: The external reference. Ensure that the asset data uses a media type of
|
||||
`application/pkcs1` or `application/pem` to correctly identify the type of encoded
|
||||
certificate. If the asset data includes a `ContentType` sub-key, set it to the
|
||||
corresponding media type.
|
||||
content: The external reference. Ensure the asset data contains exactly one certificate.
|
||||
If the PEM data contains more than one certificate, the system installs the first
|
||||
certificate and ignores the rest. Ensure that the asset data uses a media type
|
||||
of `application/pkcs1` or `application/pem` to correctly identify the type of
|
||||
encoded certificate. If the asset data includes a `ContentType` sub-key, set it
|
||||
to the corresponding media type.
|
||||
subkeys:
|
||||
- key: DataURL
|
||||
title: Data URL
|
||||
|
||||
@@ -426,15 +426,15 @@ payloadkeys:
|
||||
type: <array>
|
||||
presence: optional
|
||||
content: |-
|
||||
The policy to apply when using Platform SSO at FileVault unlock on a Mac with Apple silicon. Applies when `AuthenticationMethod` is `Password`.
|
||||
The policy to apply when using Platform SSO at FileVault unlock on a Mac with Apple silicon.
|
||||
|
||||
* `AttemptAuthentication`: The device attempts Platform SSO authentication before proceeding. If offline, unlock continues if the local account password matches. If online and the credential is incorrect, then the device requires a successful Platform SSO authentication is required, even if taken offline.
|
||||
* `RequireAuthentication`: The device requires Platform SSO authentication before proceeding. If the device is offline and `AllowOfflineGracePeriod` is enabled, then the device uses the offline `OfflineGracePeriod` to determine if the user can proceed or not. If online and the credential is incorrect, then the device requires a valid Platform SSO authentication to proceed, regardless of the `OfflineGracePeriod`. If the account isn't registered for Platform SSO and `AllowAuthenticationGracePeriod` is enabled, then the device uses `AuthenticationGracePeriod` to determine if the user can proceed or not.
|
||||
* `AllowOfflineGracePeriod`: The device allows the use of the `OfflineGracePeriod` when `RequireAuthentication` is enabled. If `AllowOfflineGracePeriod` isn't set, then the device denies offline access.
|
||||
* `AllowAuthenticationGracePeriod`: The device allows the use of the `AuthenticationGracePeriod` for other local accounts when `RequireAuthentication` is enabled. The `AuthenticationGracePeriod` starts when any of the policies are updated. If `AllowAuthenticationGracePeriod` isn't set, then the device denies unregistered account access.
|
||||
* `RequireTouchID`: The device requires the use of Touch ID (and not Apple Watch) for File Vault unlock.
|
||||
* `RequireTouchIDOrWatch`: The device requires the use of Touch ID or Apple Watch for File Vault unlock.
|
||||
* `AllowOpenIDForTouchIDFallback`: The device allows web login as a fallback if touchID fails or isn't available.
|
||||
* `AttemptAuthentication`: The device attempts Platform SSO authentication before proceeding. If offline, unlock continues if the local account password matches. If online and the credential is incorrect, then the device requires a successful Platform SSO authentication is required, even if taken offline. Only use when `AuthenticationMethod` is `Password`.
|
||||
* `RequireAuthentication`: The device requires Platform SSO authentication before proceeding. If the device is offline and `AllowOfflineGracePeriod` is enabled, then the device uses the offline `OfflineGracePeriod` to determine if the user can proceed or not. If online and the credential is incorrect, then the device requires a valid Platform SSO authentication to proceed, regardless of the `OfflineGracePeriod`. If the account isn't registered for Platform SSO and `AllowAuthenticationGracePeriod` is enabled, then the device uses `AuthenticationGracePeriod` to determine if the user can proceed or not. Only use when `AuthenticationMethod` is `Password`.
|
||||
* `AllowOfflineGracePeriod`: The device allows the use of the `OfflineGracePeriod`. If `AllowOfflineGracePeriod` isn't set, then the device denies offline access. Only use when `AuthenticationMethod` is `Password` and `RequireAuthentication` is enabled, or `AuthenticationMethod` is `OpenID`.
|
||||
* `AllowAuthenticationGracePeriod`: The device allows the use of the `AuthenticationGracePeriod` for other local accounts when `RequireAuthentication` is enabled. The `AuthenticationGracePeriod` starts when any of the policies are updated. If `AllowAuthenticationGracePeriod` isn't set, then the device denies unregistered account access. Only use when `AuthenticationMethod` is `Password`.
|
||||
* `RequireTouchID`: The device requires the use of Touch ID (and not Apple Watch) for FileVault unlock. Only use when `AuthenticationMethod` is `Password` or `UserSecureEnclaveKey`.
|
||||
* `RequireTouchIDOrWatch`: The device requires the use of Touch ID or Apple Watch for FileVault unlock. Only use when `AuthenticationMethod` is `Password` or `UserSecureEnclaveKey`.
|
||||
* `AllowOpenIDForTouchIDFallback`: The device allows web login as a fallback if Touch ID fails or isn't available. Only use when `AuthenticationMethod` is `Password` or `UserSecureEnclaveKey`.
|
||||
subkeys:
|
||||
- key: policy
|
||||
type: <string>
|
||||
@@ -453,15 +453,15 @@ payloadkeys:
|
||||
type: <array>
|
||||
presence: optional
|
||||
content: |-
|
||||
The policy to apply when using Platform SSO at the Login Window. Applies when `AuthenticationMethod` is `Password`.
|
||||
The policy to apply when using Platform SSO at the Login Window.
|
||||
|
||||
* `AttemptAuthentication`: The device attempts Platform SSO authentication before proceeding. If offline, login continues if the local account password matches. If online and the credential is incorrect, then the device requires a successful Platform SSO authentication to proceed, even if taken offline.
|
||||
* `RequireAuthentication`: The device requires Platform SSO authentication before proceeding. If the device is offline and `AllowOfflineGracePeriod` is enabled, then the device uses the offline `OfflineGracePeriod` to determine if the user can proceed or not. If online and the credential is incorrect, then the device requires a valid Platform SSO authentication to proceed, regardless of the `OfflineGracePeriod`. If the account isn't registered for Platform SSO and `AllowAuthenticationGracePeriod` is enabled, then the device uses the `AuthenticationGracePeriod` to determine if the user can proceed or not.
|
||||
* `AllowOfflineGracePeriod`: The device allows the use of the `OfflineGracePeriod` when `RequireAuthentication` is enabled. If `AllowOfflineGracePeriod` isn't set, then the device denies offline access. Applies to web login and all offline passwords.
|
||||
* `AllowAuthenticationGracePeriod`: The device allows the use of the `AuthenticationGracePeriod` for other local accounts when `RequireAuthentication` is enabled. The `AuthenticationGracePeriod` starts when any of the policies have been updated. If `AllowAuthenticationGracePeriod` isn't set, then the device denies unregistered account access.
|
||||
* `RequireTouchID`: The device requires the use of Touch ID (and not Apple Watch) for login.
|
||||
* `RequireTouchIDOrWatch`: The device requires the use of Touch ID or Apple Watch for login.
|
||||
* `AllowOpenIDForTouchIDFallback`: The device allows web login as fallback if touchID fails or isn't available.
|
||||
* `AttemptAuthentication`: The device attempts Platform SSO authentication before proceeding. If offline, login continues if the local account password matches. If online and the credential is incorrect, then the device requires a successful Platform SSO authentication to proceed, even if taken offline. Only use when `AuthenticationMethod` is `Password`.
|
||||
* `RequireAuthentication`: The device requires Platform SSO authentication before proceeding. If the device is offline and `AllowOfflineGracePeriod` is enabled, then the device uses the offline `OfflineGracePeriod` to determine if the user can proceed or not. If online and the credential is incorrect, then the device requires a valid Platform SSO authentication to proceed, regardless of the `OfflineGracePeriod`. If the account isn't registered for Platform SSO and `AllowAuthenticationGracePeriod` is enabled, then the device uses the `AuthenticationGracePeriod` to determine if the user can proceed or not. Only use when `AuthenticationMethod` is `Password`.
|
||||
* `AllowOfflineGracePeriod`: The device allows the use of the `OfflineGracePeriod`. If `AllowOfflineGracePeriod` isn't set, then the device denies offline access. Only use when `AuthenticationMethod` is `Password` and `RequireAuthentication` is enabled, or `AuthenticationMethod` is `OpenID`.
|
||||
* `AllowAuthenticationGracePeriod`: The device allows the use of the `AuthenticationGracePeriod` for other local accounts when `RequireAuthentication` is enabled. The `AuthenticationGracePeriod` starts when any of the policies have been updated. If `AllowAuthenticationGracePeriod` isn't set, then the device denies unregistered account access. Only use when `AuthenticationMethod` is `Password`.
|
||||
* `RequireTouchID`: The device requires the use of Touch ID (and not Apple Watch) for login. Only use when `AuthenticationMethod` is `Password` or `UserSecureEnclaveKey`.
|
||||
* `RequireTouchIDOrWatch`: The device requires the use of Touch ID or Apple Watch for login. Only use when `AuthenticationMethod` is `Password` or `UserSecureEnclaveKey`.
|
||||
* `AllowOpenIDForTouchIDFallback`: The device allows web login as fallback if Touch ID fails or isn't available. Only use when `AuthenticationMethod` is `Password` or `UserSecureEnclaveKey`.
|
||||
subkeys:
|
||||
- key: policy
|
||||
type: <string>
|
||||
@@ -480,16 +480,16 @@ payloadkeys:
|
||||
type: <array>
|
||||
presence: optional
|
||||
content: |-
|
||||
The policy to apply when using Platform SSO at screensaver unlock. Applies when `AuthenticationMethod` is `Password`. later.
|
||||
The policy to apply when using Platform SSO at screensaver unlock.
|
||||
|
||||
* `AttemptAuthentication`: The device attempts Platform SSO authentication before proceeding. If offline, unlock will continue if the local account password matches. If online and the credential is incorrect, then the device requires a successful Platform SSO authentication to proceed, even if taken offline.
|
||||
* `RequireAuthentication`: The device requires Platform SSO authentication before proceeding. If the device is offline and `AllowOfflineGracePeriod` is enabled, then the offline `OfflineGracePeriod` is used to determine if the user can proceed or not. If online and the credential is incorrect, then the device requires a valid Platform SSO authentication to proceed regardless of the `OfflineGracePeriod`. If the account isn't registered for Platform SSO and `AllowAuthenticationGracePeriod` is enabled, then the device uses `AuthenticationGracePeriod` to determine if the user can proceed or not.
|
||||
* `AllowOfflineGracePeriod`: The device allows the use of the `OfflineGracePeriod` when `RequireAuthentication` is enabled. If `AllowOfflineGracePeriod` isn't set, then the device denies offline access.
|
||||
* `AllowAuthenticationGracePeriod`: The device allows the use of the `AuthenticationGracePeriod` for other local accounts when `RequireAuthentication` is enabled. The `AuthenticationGracePeriod` starts when any of the policies have been updated. If `AllowAuthenticationGracePeriod` isn't set, then the device denies the unregistered account access.
|
||||
* `AllowTouchIDOrWatchForUnlock`: The device allows TouchID or Watch to unlock the screensaver instead of Platform SSO authentication when `RequireAuthentication` is enabled.
|
||||
* `RequireTouchID`: The device requires the use of Touch ID (and not Apple Watch) for unlock.
|
||||
* `RequireTouchIDOrWatch`: RThe device requires the use of Touch ID or Apple Watch for unlock.
|
||||
* `AllowOpenIDForTouchIDFallback`: The device allows web login as fallback if touchID fails or isn't available.
|
||||
* `AttemptAuthentication`: The device attempts Platform SSO authentication before proceeding. If offline, unlock will continue if the local account password matches. If online and the credential is incorrect, then the device requires a successful Platform SSO authentication to proceed, even if taken offline. Only use when `AuthenticationMethod` is `Password`.
|
||||
* `RequireAuthentication`: The device requires Platform SSO authentication before proceeding. If the device is offline and `AllowOfflineGracePeriod` is enabled, then the offline `OfflineGracePeriod` is used to determine if the user can proceed or not. If online and the credential is incorrect, then the device requires a valid Platform SSO authentication to proceed regardless of the `OfflineGracePeriod`. If the account isn't registered for Platform SSO and `AllowAuthenticationGracePeriod` is enabled, then the device uses `AuthenticationGracePeriod` to determine if the user can proceed or not. Only use when `AuthenticationMethod` is `Password`.
|
||||
* `AllowOfflineGracePeriod`: The device allows the use of the `OfflineGracePeriod`. If `AllowOfflineGracePeriod` isn't set, then the device denies offline access. Only use when `AuthenticationMethod` is `Password` and `RequireAuthentication` is enabled, or `AuthenticationMethod` is `OpenID`.
|
||||
* `AllowAuthenticationGracePeriod`: The device allows the use of the `AuthenticationGracePeriod` for other local accounts when `RequireAuthentication` is enabled. The `AuthenticationGracePeriod` starts when any of the policies have been updated. If `AllowAuthenticationGracePeriod` isn't set, then the device denies the unregistered account access. Only use when `AuthenticationMethod` is `Password`.
|
||||
* `AllowTouchIDOrWatchForUnlock`: The device allows Touch ID or Apple Watch to unlock the screensaver instead of Platform SSO authentication when `RequireAuthentication` is enabled. Only use when `AuthenticationMethod` is `Password`.
|
||||
* `RequireTouchID`: The device requires the use of Touch ID (and not Apple Watch) for unlock. Only use when `AuthenticationMethod` is `Password` or `UserSecureEnclaveKey`.
|
||||
* `RequireTouchIDOrWatch`: The device requires the use of Touch ID or Apple Watch for unlock. Only use when `AuthenticationMethod` is `Password` or `UserSecureEnclaveKey`.
|
||||
* `AllowOpenIDForTouchIDFallback`: The device allows web login as fallback if Touch ID fails or isn't available. Only use when `AuthenticationMethod` is `Password` or `UserSecureEnclaveKey`.
|
||||
subkeys:
|
||||
- key: policy
|
||||
type: <string>
|
||||
@@ -508,13 +508,14 @@ payloadkeys:
|
||||
title: Offline grace period
|
||||
type: <integer>
|
||||
presence: optional
|
||||
content: The amount of time after the last successful Platform SSO login for
|
||||
using a local account password offline. Required when setting `AllowOfflineGracePeriod`.
|
||||
content: The amount of time (in seconds) after the last successful Platform
|
||||
SSO login for using a local account password offline. Required when setting
|
||||
`AllowOfflineGracePeriod`.
|
||||
- key: AuthenticationGracePeriod
|
||||
title: Authentication grace period
|
||||
type: <integer>
|
||||
presence: optional
|
||||
content: The amount of time after receiving or updating a `Policies.FileVault`,
|
||||
content: The amount of time (in seconds) after receiving or updating a `Policies.FileVault`,
|
||||
`Policies.Login`, or `Policies.Unlock` that the system can use unregistered
|
||||
local accounts. Required when `AllowAuthenticationGracePeriod` is set.
|
||||
- key: NonPlatformSSOAccounts
|
||||
|
||||
@@ -121,7 +121,7 @@ payloadkeys:
|
||||
tvOS:
|
||||
introduced: n/a
|
||||
visionOS:
|
||||
introduced: n/a
|
||||
introduced: '27.0'
|
||||
watchOS:
|
||||
introduced: n/a
|
||||
type: <boolean>
|
||||
|
||||
@@ -103,7 +103,7 @@ examples:
|
||||
files:
|
||||
- tab: New or updated account
|
||||
description: Reports a new or updated account.
|
||||
file: data/docc-examples/remotemanagementmodel/status/account.list.caldav/example1.json
|
||||
file: examples/declarative/status/account.list.caldav/example1.json
|
||||
- tab: Removed account
|
||||
description: Reports a removed account.
|
||||
file: data/docc-examples/remotemanagementmodel/status/account.list.caldav/example2.json
|
||||
file: examples/declarative/status/account.list.caldav/example2.json
|
||||
|
||||
@@ -92,7 +92,7 @@ examples:
|
||||
files:
|
||||
- tab: New or updated account
|
||||
description: Reports a new or updated account.
|
||||
file: data/docc-examples/remotemanagementmodel/status/account.list.carddav/example1.json
|
||||
file: examples/declarative/status/account.list.carddav/example1.json
|
||||
- tab: Removed account
|
||||
description: Reports a removed account.
|
||||
file: data/docc-examples/remotemanagementmodel/status/account.list.carddav/example2.json
|
||||
file: examples/declarative/status/account.list.carddav/example2.json
|
||||
|
||||
@@ -122,7 +122,7 @@ examples:
|
||||
files:
|
||||
- tab: New or updated account
|
||||
description: Reports a new or updated account.
|
||||
file: data/docc-examples/remotemanagementmodel/status/account.list.exchange/example1.json
|
||||
file: examples/declarative/status/account.list.exchange/example1.json
|
||||
- tab: Removed account
|
||||
description: Reports a removed account.
|
||||
file: data/docc-examples/remotemanagementmodel/status/account.list.exchange/example2.json
|
||||
file: examples/declarative/status/account.list.exchange/example2.json
|
||||
|
||||
@@ -106,7 +106,7 @@ examples:
|
||||
files:
|
||||
- tab: New or updated account
|
||||
description: Reports a new or updated account.
|
||||
file: data/docc-examples/remotemanagementmodel/status/account.list.google/example1.json
|
||||
file: examples/declarative/status/account.list.google/example1.json
|
||||
- tab: Removed account
|
||||
description: Reports a removed account.
|
||||
file: data/docc-examples/remotemanagementmodel/status/account.list.google/example2.json
|
||||
file: examples/declarative/status/account.list.google/example2.json
|
||||
|
||||
@@ -99,7 +99,7 @@ examples:
|
||||
files:
|
||||
- tab: New or updated account
|
||||
description: Reports a new or updated account.
|
||||
file: data/docc-examples/remotemanagementmodel/status/account.list.ldap/example1.json
|
||||
file: examples/declarative/status/account.list.ldap/example1.json
|
||||
- tab: Removed account
|
||||
description: Reports a removed account.
|
||||
file: data/docc-examples/remotemanagementmodel/status/account.list.ldap/example2.json
|
||||
file: examples/declarative/status/account.list.ldap/example2.json
|
||||
|
||||
@@ -104,7 +104,7 @@ examples:
|
||||
files:
|
||||
- tab: New or updated account
|
||||
description: Reports a new or updated account.
|
||||
file: data/docc-examples/remotemanagementmodel/status/account.list.mail.incoming/example1.json
|
||||
file: examples/declarative/status/account.list.mail.incoming/example1.json
|
||||
- tab: Removed account
|
||||
description: Reports a removed account.
|
||||
file: data/docc-examples/remotemanagementmodel/status/account.list.mail.incoming/example2.json
|
||||
file: examples/declarative/status/account.list.mail.incoming/example2.json
|
||||
|
||||
@@ -92,7 +92,7 @@ examples:
|
||||
files:
|
||||
- tab: New or updated account
|
||||
description: Reports a new or updated account.
|
||||
file: data/docc-examples/remotemanagementmodel/status/account.list.mail.outgoing/example1.json
|
||||
file: examples/declarative/status/account.list.mail.outgoing/example1.json
|
||||
- tab: Removed account
|
||||
description: Reports a removed account.
|
||||
file: data/docc-examples/remotemanagementmodel/status/account.list.mail.outgoing/example2.json
|
||||
file: examples/declarative/status/account.list.mail.outgoing/example2.json
|
||||
|
||||
@@ -93,7 +93,7 @@ examples:
|
||||
files:
|
||||
- tab: New or updated account
|
||||
description: Reports a new or updated account.
|
||||
file: data/docc-examples/remotemanagementmodel/status/account.list.subscribed-calendar/example1.json
|
||||
file: examples/declarative/status/account.list.subscribed-calendar/example1.json
|
||||
- tab: Removed account
|
||||
description: Reports a removed account.
|
||||
file: data/docc-examples/remotemanagementmodel/status/account.list.subscribed-calendar/example2.json
|
||||
file: examples/declarative/status/account.list.subscribed-calendar/example2.json
|
||||
|
||||
@@ -273,7 +273,7 @@ examples:
|
||||
files:
|
||||
- tab: New or updated app
|
||||
description: Reports a new or updated app.
|
||||
file: data/docc-examples/remotemanagementmodel/status/app.managed.list/example1.json
|
||||
file: examples/declarative/status/app.managed.list/example1.json
|
||||
- tab: Removed app
|
||||
description: Reports a removed app.
|
||||
file: data/docc-examples/remotemanagementmodel/status/app.managed.list/example2.json
|
||||
file: examples/declarative/status/app.managed.list/example2.json
|
||||
|
||||
@@ -97,4 +97,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/content-cache.info/example1.json
|
||||
- file: examples/declarative/status/content-cache.info/example1.json
|
||||
|
||||
@@ -70,7 +70,7 @@ examples:
|
||||
files:
|
||||
- tab: New or updated parent
|
||||
description: Reports a new or updated parent.
|
||||
file: data/docc-examples/remotemanagementmodel/status/content-cache.parents/example1.json
|
||||
file: examples/declarative/status/content-cache.parents/example1.json
|
||||
- tab: Removed parent
|
||||
description: Reports a removed parent.
|
||||
file: data/docc-examples/remotemanagementmodel/status/content-cache.parents/example2.json
|
||||
file: examples/declarative/status/content-cache.parents/example2.json
|
||||
|
||||
@@ -76,7 +76,7 @@ examples:
|
||||
files:
|
||||
- tab: New or updated peer
|
||||
description: Reports a new or updated peer.
|
||||
file: data/docc-examples/remotemanagementmodel/status/content-cache.peers/example1.json
|
||||
file: examples/declarative/status/content-cache.peers/example1.json
|
||||
- tab: Removed peer
|
||||
description: Reports a removed peer.
|
||||
file: data/docc-examples/remotemanagementmodel/status/content-cache.peers/example2.json
|
||||
file: examples/declarative/status/content-cache.peers/example2.json
|
||||
|
||||
@@ -156,4 +156,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/content-cache.status/example1.json
|
||||
- file: examples/declarative/status/content-cache.status/example1.json
|
||||
|
||||
@@ -55,4 +55,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/device.identifier.serial-number/example1.json
|
||||
- file: examples/declarative/status/device.identifier.serial-number/example1.json
|
||||
|
||||
@@ -57,4 +57,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/device.identifier.udid/example1.json
|
||||
- file: examples/declarative/status/device.identifier.udid/example1.json
|
||||
|
||||
@@ -58,4 +58,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/device.model.family/example1.json
|
||||
- file: examples/declarative/status/device.model.family/example1.json
|
||||
|
||||
@@ -62,4 +62,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/device.model.identifier/example1.json
|
||||
- file: examples/declarative/status/device.model.identifier/example1.json
|
||||
|
||||
@@ -59,4 +59,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/device.model.marketing-name/example1.json
|
||||
- file: examples/declarative/status/device.model.marketing-name/example1.json
|
||||
|
||||
@@ -58,4 +58,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/device.model.number/example1.json
|
||||
- file: examples/declarative/status/device.model.number/example1.json
|
||||
|
||||
@@ -58,4 +58,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/device.operating-system.build-version/example1.json
|
||||
- file: examples/declarative/status/device.operating-system.build-version/example1.json
|
||||
|
||||
@@ -58,4 +58,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/device.operating-system.family/example1.json
|
||||
- file: examples/declarative/status/device.operating-system.family/example1.json
|
||||
|
||||
@@ -59,4 +59,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/device.operating-system.marketing-name/example1.json
|
||||
- file: examples/declarative/status/device.operating-system.marketing-name/example1.json
|
||||
|
||||
@@ -60,4 +60,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/device.operating-system.supplemental.build-version/example1.json
|
||||
- file: examples/declarative/status/device.operating-system.supplemental.build-version/example1.json
|
||||
|
||||
@@ -60,4 +60,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/device.operating-system.supplemental.extra-version/example1.json
|
||||
- file: examples/declarative/status/device.operating-system.supplemental.extra-version/example1.json
|
||||
|
||||
@@ -58,4 +58,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/device.operating-system.version/example1.json
|
||||
- file: examples/declarative/status/device.operating-system.version/example1.json
|
||||
|
||||
@@ -59,4 +59,4 @@ notes:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/device.power.battery-health/example1.json
|
||||
- file: examples/declarative/status/device.power.battery-health/example1.json
|
||||
|
||||
@@ -125,4 +125,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/device.system.health/example1.json
|
||||
- file: examples/declarative/status/device.system.health/example1.json
|
||||
|
||||
@@ -27,4 +27,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/diskmanagement.filevault.enabled/example1.json
|
||||
- file: examples/declarative/status/diskmanagement.filevault.enabled/example1.json
|
||||
|
||||
@@ -39,4 +39,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/enhanced-logging.applecare-token/example1.json
|
||||
- file: examples/declarative/status/enhanced-logging.applecare-token/example1.json
|
||||
|
||||
@@ -61,4 +61,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/enhanced-logging.status/example1.json
|
||||
- file: examples/declarative/status/enhanced-logging.status/example1.json
|
||||
|
||||
@@ -40,4 +40,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/enhanced-logging.timestamp/example1.json
|
||||
- file: examples/declarative/status/enhanced-logging.timestamp/example1.json
|
||||
|
||||
@@ -145,4 +145,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/management.client-capabilities/example1.json
|
||||
- file: examples/declarative/status/management.client-capabilities/example1.json
|
||||
|
||||
@@ -171,4 +171,4 @@ notes:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/management.declarations/example1.json
|
||||
- file: examples/declarative/status/management.declarations/example1.json
|
||||
|
||||
@@ -120,7 +120,7 @@ examples:
|
||||
files:
|
||||
- tab: New or updated app
|
||||
description: Reports a new or updated app.
|
||||
file: data/docc-examples/remotemanagementmodel/status/mdm.app/example1.json
|
||||
file: examples/declarative/status/mdm.app/example1.json
|
||||
- tab: Removed app
|
||||
description: Reports a removed app.
|
||||
file: data/docc-examples/remotemanagementmodel/status/mdm.app/example2.json
|
||||
file: examples/declarative/status/mdm.app/example2.json
|
||||
|
||||
@@ -64,4 +64,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/mdm.enrollment-type/example1.json
|
||||
- file: examples/declarative/status/mdm.enrollment-type/example1.json
|
||||
|
||||
@@ -50,4 +50,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/mdm.is-awaiting-configuration/example1.json
|
||||
- file: examples/declarative/status/mdm.is-awaiting-configuration/example1.json
|
||||
|
||||
@@ -40,4 +40,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/mdm.is-return-to-service/example1.json
|
||||
- file: examples/declarative/status/mdm.is-return-to-service/example1.json
|
||||
|
||||
@@ -32,4 +32,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/mdm.is-shared-ipad/example1.json
|
||||
- file: examples/declarative/status/mdm.is-shared-ipad/example1.json
|
||||
|
||||
@@ -54,4 +54,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/mdm.push-magic/example1.json
|
||||
- file: examples/declarative/status/mdm.push-magic/example1.json
|
||||
|
||||
@@ -54,4 +54,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/mdm.push-token/example1.json
|
||||
- file: examples/declarative/status/mdm.push-token/example1.json
|
||||
|
||||
@@ -78,4 +78,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/migration-assistant.report/example1.json
|
||||
- file: examples/declarative/status/migration-assistant.report/example1.json
|
||||
|
||||
@@ -40,4 +40,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/migration-assistant.state/example1.json
|
||||
- file: examples/declarative/status/migration-assistant.state/example1.json
|
||||
|
||||
@@ -135,7 +135,7 @@ examples:
|
||||
files:
|
||||
- tab: New or updated package
|
||||
description: Reports a new or updated package.
|
||||
file: data/docc-examples/remotemanagementmodel/status/package.list/example1.json
|
||||
file: examples/declarative/status/package.list/example1.json
|
||||
- tab: Removed package
|
||||
description: Reports a removed package.
|
||||
file: data/docc-examples/remotemanagementmodel/status/package.list/example2.json
|
||||
file: examples/declarative/status/package.list/example2.json
|
||||
|
||||
@@ -48,4 +48,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/passcode.is-compliant/example1.json
|
||||
- file: examples/declarative/status/passcode.is-compliant/example1.json
|
||||
|
||||
@@ -49,4 +49,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/passcode.is-present/example1.json
|
||||
- file: examples/declarative/status/passcode.is-present/example1.json
|
||||
|
||||
@@ -63,7 +63,7 @@ examples:
|
||||
files:
|
||||
- tab: New or updated connection group
|
||||
description: Reports a new or updated connection group.
|
||||
file: data/docc-examples/remotemanagementmodel/status/screensharing.connection.group.unresolved-connection/example1.json
|
||||
file: examples/declarative/status/screensharing.connection.group.unresolved-connection/example1.json
|
||||
- tab: Removed connection group
|
||||
description: Reports a removed connection group.
|
||||
file: data/docc-examples/remotemanagementmodel/status/screensharing.connection.group.unresolved-connection/example2.json
|
||||
file: examples/declarative/status/screensharing.connection.group.unresolved-connection/example2.json
|
||||
|
||||
@@ -101,7 +101,7 @@ examples:
|
||||
files:
|
||||
- tab: New or updated certificate
|
||||
description: Reports a new or updated certificate.
|
||||
file: data/docc-examples/remotemanagementmodel/status/security.certificate.list/example1.json
|
||||
file: examples/declarative/status/security.certificate.list/example1.json
|
||||
- tab: Removed certificate
|
||||
description: Reports a removed certificate.
|
||||
file: data/docc-examples/remotemanagementmodel/status/security.certificate.list/example2.json
|
||||
file: examples/declarative/status/security.certificate.list/example2.json
|
||||
|
||||
@@ -36,4 +36,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/security.lockdown-mode/example1.json
|
||||
- file: examples/declarative/status/security.lockdown-mode/example1.json
|
||||
|
||||
@@ -147,7 +147,7 @@ examples:
|
||||
files:
|
||||
- tab: New or updated task
|
||||
description: Reports a new or updated background task.
|
||||
file: data/docc-examples/remotemanagementmodel/status/services.background-task/example1.json
|
||||
file: examples/declarative/status/services.background-task/example1.json
|
||||
- tab: Removed task
|
||||
description: Reports a removed background task.
|
||||
file: data/docc-examples/remotemanagementmodel/status/services.background-task/example2.json
|
||||
file: examples/declarative/status/services.background-task/example2.json
|
||||
|
||||
@@ -35,4 +35,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/softwareupdate.beta-enrollment/example1.json
|
||||
- file: examples/declarative/status/softwareupdate.beta-enrollment/example1.json
|
||||
|
||||
@@ -45,4 +45,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/softwareupdate.device-id/example1.json
|
||||
- file: examples/declarative/status/softwareupdate.device-id/example1.json
|
||||
|
||||
@@ -65,4 +65,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/softwareupdate.failure-reason/example1.json
|
||||
- file: examples/declarative/status/softwareupdate.failure-reason/example1.json
|
||||
|
||||
@@ -83,4 +83,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/softwareupdate.install-reason/example1.json
|
||||
- file: examples/declarative/status/softwareupdate.install-reason/example1.json
|
||||
|
||||
@@ -57,4 +57,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/softwareupdate.install-state/example1.json
|
||||
- file: examples/declarative/status/softwareupdate.install-state/example1.json
|
||||
|
||||
@@ -66,4 +66,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/softwareupdate.pending-version/example1.json
|
||||
- file: examples/declarative/status/softwareupdate.pending-version/example1.json
|
||||
|
||||
@@ -36,4 +36,4 @@ notes:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/statusreason/example1.json
|
||||
- file: examples/declarative/status/statusreason/example1.json
|
||||
|
||||
@@ -75,4 +75,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/test.array-value/example1.json
|
||||
- file: examples/declarative/status/test.array-value/example1.json
|
||||
|
||||
@@ -58,4 +58,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/test.boolean-value/example1.json
|
||||
- file: examples/declarative/status/test.boolean-value/example1.json
|
||||
|
||||
@@ -70,4 +70,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/test.dictionary-value/example1.json
|
||||
- file: examples/declarative/status/test.dictionary-value/example1.json
|
||||
|
||||
@@ -58,4 +58,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/test.error-value/example1.json
|
||||
- file: examples/declarative/status/test.error-value/example1.json
|
||||
|
||||
@@ -58,4 +58,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/test.integer-value/example1.json
|
||||
- file: examples/declarative/status/test.integer-value/example1.json
|
||||
|
||||
@@ -58,4 +58,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/test.real-value/example1.json
|
||||
- file: examples/declarative/status/test.real-value/example1.json
|
||||
|
||||
@@ -58,4 +58,4 @@ payloadkeys:
|
||||
examples:
|
||||
- title: Status item example
|
||||
files:
|
||||
- file: data/docc-examples/remotemanagementmodel/status/test.string-value/example1.json
|
||||
- file: examples/declarative/status/test.string-value/example1.json
|
||||
|
||||
Reference in New Issue
Block a user