google-api-python-client 2.176.0__py3-none-any.whl → 2.178.0__py3-none-any.whl

googleapiclient/discovery_cache/documents/androidenterprise.v1.json

@@ -2691,7 +2691,7 @@
 }
 }
 },
-"revision": "20250610",
+"revision": "20250720",
 "rootUrl": "https://androidenterprise.googleapis.com/",
 "schemas": {
 "Administrator": {
@@ -3342,6 +3342,10 @@
 ],
 "type": "string"
 },
+"googleAuthenticationOptions": {
+"$ref": "EnrollmentTokenGoogleAuthenticationOptions",
+"description": "[Optional] Provides options related to Google authentication during the enrollment."
+},
 "token": {
 "description": "The token value that's passed to the device and authorizes the device to enroll. This is a read-only field generated by the server.",
 "type": "string"
@@ -3349,6 +3353,31 @@
 },
 "type": "object"
 },
+"EnrollmentTokenGoogleAuthenticationOptions": {
+"description": "Options for Google authentication during the enrollment.",
+"id": "EnrollmentTokenGoogleAuthenticationOptions",
+"properties": {
+"authenticationRequirement": {
+"description": "[Optional] Specifies whether user should authenticate with Google during enrollment. This setting, if specified,`GoogleAuthenticationSettings` specified for the enterprise resource is ignored for devices enrolled with this token.",
+"enum": [
+"authenticationRequirementUnspecified",
+"optional",
+"required"
+],
+"enumDescriptions": [
+"The value is unused.",
+"Google authentication is optional for the user. This means the user can choose to skip Google authentication during enrollment.",
+"Google authentication is required for the user. This means the user must authenticate with a Google account to proceed."
+],
+"type": "string"
+},
+"requiredAccountEmail": {
+"description": "[Optional] Specifies the managed Google account that the user must use during enrollment.`AuthenticationRequirement` must be set to`REQUIRED` if this field is set.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "Enterprise": {
 "description": "An Enterprises resource represents the binding between an EMM and a specific organization. That binding can be instantiated in one of two different ways using this API as follows: - For Google managed domain customers, the process involves using Enterprises.enroll and Enterprises.setAccount (in conjunction with artifacts obtained from the Admin console and the Google API Console) and submitted to the EMM through a more-or-less manual process. - For managed Google Play Accounts customers, the process involves using Enterprises.generateSignupUrl and Enterprises.completeSignup in conjunction with the managed Google Play sign-up UI (Google-provided mechanism) to create the binding without manual steps. As an EMM, you can support either or both approaches in your EMM console. See Create an Enterprise for details.",
 "id": "Enterprise",

googleapiclient/discovery_cache/documents/androidmanagement.v1.json

@@ -1260,7 +1260,7 @@
 }
 }
 },
-"revision": "20250702",
+"revision": "20250714",
 "rootUrl": "https://androidmanagement.googleapis.com/",
 "schemas": {
 "AdbShellCommandEvent": {
@@ -6085,8 +6085,8 @@ false
 "On Android 8 and below, only the network location provider is enabled. On Android 9 and above, this is equivalent to LOCATION_ENFORCED.",
 "On Android 8 and below, location setting and accuracy are disabled. On Android 9 and above, this is equivalent to LOCATION_DISABLED.",
 "Location setting is not restricted on the device. No specific behavior is set or enforced.",
-"Enable location setting on the device.",
-"Disable location setting on the device."
+"Enable location setting on the device. Important: On Android 11 and above, work profiles on company-owned devices cannot directly enforce enabling of location services. When LOCATION_ENFORCED is set, then a NonComplianceDetail with USER_ACTION is reported. Compliance can only be restored once the user manually turns on location services through the device's Settings application. ",
+"Disable location setting on the device. Important: On Android 11 and above, work profiles on company-owned devices cannot directly enforce disabling of location services. When LOCATION_DISABLED is set, then a nonComplianceDetail with USER_ACTION is reported. Compliance can only be restored once the user manually turns off location services through the device's Settings application. "
 ],
 "type": "string"
 },