Project

General

Profile

Actions

Bug #10552

closed

Android fully managed enrollment is not working

Bug #10552: Android fully managed enrollment is not working

Added by Arshana Atapattu almost 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Critical
Start date:
03/06/2024
Due date:
06/06/2024
% Done:

10%

Estimated time:
CallRef:
Device Type:

Description

Environment details
Staging server(6.1.0)
Agent version: 4.05.00.10

Prerequisites
none

Steps
Enroll a device as Fully manged

Description

Device details: Android 11, Galaxy M02 also on a xiaomi redmi 10A
Agent: io.entgra.proprietary.android.agent.release-4.05.00.09

Tried to enroll a device as fully managed. Did not enroll.
Tried methods 1) Fully Managed QR through agent and 2) Fully Managed QR after Factory reset [4].

for the 1st method the payload was this [1]

When scanned, at first it says device is already setup [2] (Note: device was factory reseted and was boot up to menu)
and after completing enrollment procedure it shows setup is completed [3]. but after open the agent, enrollment has not done( it again shows the fist page of the enrollment)
There was no error log on carbon log and couldn't find any error logs related to enrollment in log cat.

Result

[1] {"android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_DOWNLOAD_LOCATION":"https://uem.mgt.entgra.net/api/application-mgt/v1.0/artifact/android/agent","android.app.extra.PROVISIONING_SKIP_ENCRYPTION":"false","android.app.extra.PROVISIONING_ADMIN_EXTRAS_BUNDLE":{"android.app.extra.serverIp":"https://uem.gw.entgra.net:443","android.app.extra.token":"6b2c8d5a-bdb0-40c2-b760-8b5a28b6f2ba","android.app.extra.token.expiry":2700,"android.app.extra.defaultOwner":"FULLY_MANAGED"},"android.app.extra.PROVISIONING_USE_MOBILE_DATA":true,"android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED":true,"enterpriseId":"LC010b821o","android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_CHECKSUM":"UgqlVe4F8WN3X4SsqpzhzBWaZ_QcWarOMoj8EU9eqig","android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME":"io.entgra.iot.agent/org.wso2.iot.agent.services.AgentDeviceAdminReceiver"}

[2]
[2]

[3]
[3]

[4]
[4]


Files

Updated by Viranga Gunarathna over 2 years ago Actions #1

  • Project changed from product-uem 6.1.0 GA to Backlog

Updated by Viranga Gunarathna over 2 years ago Actions #2

  • Project changed from Backlog to product-uem 6.1.0 GA
  • Priority changed from Critical to Medium

Updated by Sandaru Daminda over 2 years ago Actions #3

  • Due date set to 19/02/2024
  • % Done changed from 0 to 50

Updated by Sandaru Daminda over 2 years ago Actions #4

  • % Done changed from 50 to 10

Updated by Sandaru Daminda over 2 years ago Actions #5

  • Due date changed from 19/02/2024 to 15/03/2024

Updated by Arshana Atapattu over 2 years ago Actions #6

  • Description updated (diff)

Updated by Viranga Gunarathna over 2 years ago Actions #7

  • Project changed from product-uem 6.1.0 GA to product-uem 6.2.0 GA

Updated by Sandaru Daminda over 2 years ago Actions #8

  • Due date changed from 15/03/2024 to 30/04/2024
  • Start date changed from 23/01/2024 to 29/04/2024

Updated by Sandaru Daminda over 2 years ago Actions #9

  • Due date changed from 30/04/2024 to 02/05/2024

Updated by Arshana Atapattu over 2 years ago Actions #10

  • Subject changed from Android fully manged enrollment is not working to Android fully managed enrollment is not working
  • Priority changed from Medium to Critical

Updated by Sandaru Daminda over 2 years ago Actions #11

  • Due date changed from 02/05/2024 to 30/05/2024
  • Start date changed from 29/04/2024 to 27/05/2024

Updated by Sandaru Daminda over 2 years ago Actions #12

  • Due date changed from 30/05/2024 to 06/06/2024
  • Start date changed from 27/05/2024 to 03/06/2024

Updated by Arshana Atapattu over 2 years ago Actions #13

1000191665.jpg

Updated by Sandaru Daminda over 2 years ago Actions #14

Tried to reproduce it with Google Pixel and Xiaomi devices and the issue did not reproduce.
Need to check the exact device.

Updated by Sandaru Daminda over 2 years ago Actions #15

  • Status changed from New to On hold

Updated by Arshana Atapattu over 2 years ago Actions #16

  • Status changed from On hold to Closed

The method with enrolling after boot up the device with agent is not supported by Fully managed.

The enroll with retested device was not supported by device side.
It is not a agent issue.

Actions

Also available in: PDF Atom