Deploying certificates to the Quest 2
I spent some time working with the Workspace ONE XR Hub team (find out about HR Hub here) and whilst it is very simple to install a certificate to a Quest enrolled in Workspace ONE, it's not that simple to install one on a non-enrolled device.
Why would you want to install a certificate on an Oculus Quest you might ask? Well, I am a volunteer CS teacher for TEALS and the school I was working with purchased some Quest 2 headsets for the students. Unfortunately, she was unable to connect them to the school network as the network was protected by securly an needed a certificate installed on the device before it was able to connect to the network. The schools IT team were unable to help and since I had experience with the Quest 2 while working with XR Hub team I was asked if I could help.
The Quest 2 (like most VR/XR headsets) runs a version of Android AOSP heavily customized by the OEM. If I could get to the underlying O/S, I would be able to install the certificate.
Step 1: Enable Developer mode.
One a regular android device, developer mode can be enabled by tapping the build number in the device settings a number of times. A popup will then appear showing that Developer mode was enabled. Once enabled, USB debugging can be turned on and Android Debug Bridge (adb) can be used to configure the device. However, this is not a normal Android device, but Meta do offer a process to enable developer mode. The full steps are available here but basically:
- Sign up for a developer account with Meta
- Download the Meta Quest mobile app and log in with the same accout
- Pair the headset with the phone
- In the App, go to Headset Settings > Developer Mode > Enable developer mode
![]() |
![]() |
![]() |
Comments
Post a Comment