magicleap.com Copyright © 2024 Magic Leap Inc.
Device Setup
Third-Party Software Application
This process can take 5 minutes per unit. Device setup should be performed by an administrator who
sets up the device for employees. As mentioned in the MDM section, if the MDM requires a QR code, be
sure to have it available. Turn on the device with the power button, and put the headset on then go
through the rst-time device setup steps.
Whether the application used with the Magic Leap 2 is created by the enterprise or by an ISV it would
need to be added to the device. There are a few ways to transfer the APK to the device.
License Activation
Device Identity Management Setup
Once the rst-time device setup is completed, the user can now enter their license key to
unlock the enterprise features. To set up the license, enter the license key from the email with
the license key and follow these instructions. This will have to be done manually for every
device setup.
After the license is set up, all enterprise features will appear on the device UI, such as Iris ID and
OpenID Connect/OAuth2 user setup.
This feature applies to situations where the
enterprise would like Magic Leap 2 end users
to leverage their enterprise credentials to
log in to their devices. This feature must be
set up before end users log in to the device
with their credentials to ensure the connec-
tion between the device and the identity
management system is established. To set
up this feature, follow these instructions.
Note that only the MDMs that are sideload-
ed support this feature.
Once the device is set up for these enter-
prise accounts, a new user can be created
from the Settings menu or the Lock screen
by following these instructions. A total of
99 user proles are supported, and these
user proles must be manually created and
manually deleted.
Note: This login type can also be lever-
aged by applications that have set up the
identity management login type as well.
The IT administrator determines the token
renewal period. Therefore, it will ask the end
user to log in as often as the token must be
renewed.
Although not required, OAuth and PIN can
both be enabled on your device, with PIN
requested rst during an unlock sequence.
Note that this feature sits behind the other
logins. For example, a PIN would not be
required when a user logs in with enterprise
credentials. For device admin users and sec-
ondary users, credentials can be leveraged
when logging into enterprise applications.
To set this feature up, refer to this article.
1. Push the application to the device using Wi-Fi with the MDM
2. Sideload the application by connecting the Magic Leap 2 to a
computer and using the Hub. For instructions on installing and
uninstalling applications to Magic Leap 2 using this method, refer
to this article.
To Next Page
Loading...
