authentication

4 Topics

Two factor authentication impossible to set up- cant contact support
trying to set up two factor authentication on my account for access to much needed quest developer settings, only to find that meta doesn't know how to send a simple text message and that their support team built a literal freaking loop into their website to make them impossible to contact- if someone could explain to me how I can call a real person at meta who will understand me better than a machine I would really appreciate it.
the.cubed.martian
3 years ago Place Quest Development
913Views
1like
1Comment
invalid_request for some nonces / user_id when posting to user_nonce_validate
I’m following the user verification flow from meta here: https://developer.oculus.com/documentation/native/ps-ownership/#integrate-user-verification … in order to validate the identity (user id) of a user that I got through invoking the user proof sdk method ovr_User_GetUserProof(). 90% of the time, invoking the meta nonce validation endpoint results in a successful validation, when I call this: https://graph.oculus.com/user_nonce_validate using the user id and nonce from ovr_User_GetUserProof(). But for 10% of my users, I get a invalid_request from the service! I'm invoking this endpoint in a nodejs service like this: const verifyRequestPayload = { access_token: `OC|${appId}|${appSecret}`, nonce, user_id: `${userId}`, } const response = await axios.post(`${oculusServerHost}/user_nonce_validate`, verifyRequestPayload) Calling with a string or number `user_id` makes no difference; some users always end up with invalid_request response from the server. 'content-length': '190' connection: 'close', date: 'Tue, 09 May 2023 07:34:16 GMT', 'x-fb-debug': 'XXXXXXXXXXXXXXREDACTEDXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX==', 'x-fb-rev': '0000000000', 'x-fb-trace-id': 'XXREDACTEXX', 'x-fb-request-id': 'XXXXXREDACTEDXXXXXXXX', expires: 'Sat, 01 Jan 2000 00:00:00 GMT', 'cache-control': 'no-store', pragma: 'no-cache', 'strict-transport-security': 'max-age=31536000; preload; includeSubDomains', 'access-control-allow-origin': '*', 'oculus-api-version': 'v1.0', 'www-authenticate': 'OAuth "Facebook Platform" "invalid_request" "Parameter user_id: invalid user id: 9XXXXXXXXXXXXXXX"', 'content-type': 'application/json; charset=UTF-8', vary: 'Origin', (above are the response headers from meta; identifying information redacted for safety). const response = await axios.post(`${oculusServerHost}/user_nonce_validate`, verifyRequestPayload) I’ve noticed a pattern where almost all the rejected ones start with 9xxxxxxxx, and the accepted ones start with 5xxxxxxx or 6xxxxxxx. Does this make sense to anybody? Is meta systematically rejecting userids within a range, or does the nonce only apply to user ids within a particular range?
Solved
AronOlio
3 years ago Place Quest Development
4.4KViews
3likes
4Comments
Developer mode authentication
I’ve been trying for over an hour to verify my developer account, but it’s not working. I’ve entered my phone number multiple times and never got a single code sent to me. Now it says I’ve requested too many codes even though I didn’t get any. also Idk if it actually needs “my” card information or not before sending my number. kudos to Meta for making developer mode harder to access /s 🙄
smokey.skys
3 years ago Place Quest Development
751Views
0likes
0Comments
Authentication using OAuth on Quest - supported flows using browser, QR or companion app?
We have an existing enterprise app that we are porting to Quest. The app is built using Unity and an OAuth service (Azure B2C) is used for authentication. Currently, we support multiple authentication flows, including using browser based authentication and reading QR codes using the built in camera on devices where typing is inconvenient, such as Microsoft HoloLens. I'm trying to find the recommended path for secure authentication for Oculus Quest. Thing's I've tried: browser authentication does not work since the Oculus browser does not appear to allow intent-filters to open applications as per Android default behaviour, see https://forums.oculusvr.com/developer/discussion/89646/feature-request-allow-appps-to-be-launched-via-intent-filters-from-oculus-browser#latest QR authentication does not work, since no QR reading framework is available on the device like it is on other platforms (HoloLens 2 and even Windows Mixed Reality headsets), and since the cameras are not directly accessible to developers either. Quest does seem to have some provisioning for authentication through it's own companion app, but I can find no mention that we can develop our own 3rd party companion app to handle authentication this way? I'm sure there are many other developers looking to authenticate their Quest users through OAuth; how did you manage this?
anderslu
5 years ago Place Quest Development
3.1KViews
6likes
2Comments