cancel
Showing results for 
Search instead for 
Did you mean: 

How can we setup a "login with Oculus" on our game's homepage?

eraserqueen
Explorer

We have an oculus game on the store that allows users to import their personal assets (picture, video, music), and a web portal for users to upload/manage those assets. We want our users to be able to login to that portal using their Oculus account.

 

The docs for Account Linking in the Oculus Developer dashboard reference a url to start the SSO workflow that turns out to be 404: https://auth.oculus.com/sso/?redirect_uri=https://someloginuri.com/oa&organization_id=12345678123456...

 

We thought that because Oculus accounts have now been merged into Facebook/Meta accounts, we may be able to use a classic FB login to authenticate our users, but this doesn't give us access to their Oculus user id, and the FB OAuth tokens are considered invalid by the Oculus Graph API.

 

What is the up-to-date flow to authenticate oculus users on our website using their Oculus/FB/Meta account?

1 ACCEPTED SOLUTION

Accepted Solutions

Yes that's right:

- this is the link in our code: https://auth.oculus.com/sso/?redirect_uri=https://ourcompanyredirect.com/endpoint&organization_id=12...

- make sure the org id is the org id, not the app id

- make sure https://ourcompanyredirect.com/endpoint is whitelisted in the SSO page

View solution in original post

9 REPLIES 9

eraserqueen
Explorer

Ok so we had 2 issues :

- we were using AppID instead of OrgID

- we didn't had the correct url in SSO whitelist

 

With both these steps fixed, we now have a proper linking page.

certifiedmexican.20
Honored Guest

 

How do I connect Oculus to game?
 
 
Oculus Link Setup

Make sure your Quest is turned on and connected to your computer with your USB cable. From there, open the PC Oculus app and press 'Add a New Headset' and select either the original Oculus Quest or Quest 2. The app will then run you through an easy first-time setup process.

Hello, would you be so kind to share how you solved it?

Are you calling the link from your URL and added that URL to the SSO whitelist?
Thanks

Yes that's right:

- this is the link in our code: https://auth.oculus.com/sso/?redirect_uri=https://ourcompanyredirect.com/endpoint&organization_id=12...

- make sure the org id is the org id, not the app id

- make sure https://ourcompanyredirect.com/endpoint is whitelisted in the SSO page

BaskaraAccelbyte
Honored Guest

does oculus support add 'state' params to  https://auth.oculus.com/sso along with 'redirect' params. 

@eraserqueen We have a very similar context to yours; We have an Oculus game available on the store alongside a web portal designed to help users manage their account information. We want to provide users with the convenience of logging into our web portal using their Oculus account, ideally through some form of OAuth or Single Sign-On (SSO) mechanism.

We implemented a solution similar to what is explained in this thread, however we are annoyed that users are prompted to "Connect account" every time they are redirected to the SSO URL... 

So I am wondering, do you redirect your users to the SSO page (https://auth.oculus.com/sso/?redirect_uri=https://ourcompanyredirect.com/endpoint&organization_id=12...) every time they want to "Log in with Oculus" from your web portal? This seems to work, however I noticed that users are asked to "Connect account" every time they are redirected to this page... I would have expected that users would only be prompted to "Connect account" once, and that on subsequent visits they would see a normal login page.

I'd like to hear your feedback on this, and know if you have any suggestions?

Thanks!

* I posted a question on the forum about this specific subject here: https://communityforums.atmeta.com/t5/General-Development/Web-logins-using-Oculus-account/td-p/10933...

Hey amailhot, did you ever find a solution/work around/alternative? I'm currently waiting to hear back from Meta/Oculus support but based on the docs it appears the "Connect Account" issue persists and I can't find any docs saying otherwise or a different SSO URI to call.

Hey @rnmagdaleno , unfortunately it seems to be the only way to do this.

We also reached out to Meta support, and their answer was: "I don't believe the feature is meant for a 'Sign In with Quest' style functionality, but rather to attach a user to an account that you maintain on your own servers."

Also, ShapesXR uses the same Meta login flow, so we are not alone 😅