Meta Quest Attestation JWT token always Invalid Signature

Question

Hi:I am trying to use the Meta Quest Attestation API in the Unity&nbsp; projectfolowing the sample, I can get the jwt from Meta SDK all right,but whenever I verify with api with `https://graph.oculus.com/platform_integrity/verify?token=&lt;attestation_token&gt;&amp;access_token=&lt;access_token&gt;`always getting Invalid signature.I have tried on a published project's local build and an unpublished project's alpha build.Both Attestation JWT yield Invalid Signature.Do I miss something here?

chenxiz · Answer

Hi HYPER.Kao,&nbsp;Could you please paste the complete output you received from your browser after visiting the following URL below?&nbsp; &nbsp;https://graph.oculus.com/platform_integrity/verify?token=&lt;attestation_token&gt;&amp;access_token=&lt;access_token&gt;Did you use the correct access token?Is your &lt;access token&gt; in the format OC|App_ID|App_Secret?

chenxiz · Answer

Hi&nbsp;HYPER.Kao,&nbsp;Could you also make sure the token=&lt;attestation_token&gt; is not an empty string.

HYPER.Kao · Answer

if attestation_token was empty, i would get "invalid request"
and if access_token was wrong, i would get "Invalid OAuth 2.0 Access Token"

so yes, I am pretty sure those two fields werefilled with proper string

4tothefloor · Answer

Howdy!Sorry to hear that you're having trouble with the Attestation API, I get how that could be frustrating. We have some great documentation that covers the implementation of that particular API. In case you haven't checked it out already, I'll link it below. I'd recommend that you check out the Token verification section of that documentation specifically, as it mentions that error.&nbsp;Let me know if you were able to figure out the issue, and if not please feel free to reach back out and we can troubleshoot further!Meta Quest Attestation API-G

HYPER.Kao · Answer

Hi:yes, I read the doc, but the verification step still giving me invalid signature.I can get the other api access like Monetization-Add-ons Server APIs (e&nbsp;https://graph.oculus.com/$APP_ID/viewer_purchases) working.I assume the access_token part is correct just as it is setup in other api.for the attestation token read from device log,&nbsp; I can decode to read the content by jwt.iothere is some requirements or limits for attestation API that missing so I get invalid signature.

Forum Discussion

Meta Quest Attestation JWT token always Invalid Signature

9 Replies

Recent Discussions

UE5.6 passthrough windows Ques

Event-Based Push Notifications Not Being Received on Mobile Devices

Quest 3 Constant Restart Loop, Need full OTA firmware

Options for PVP Multiplayer Hosting

Max area size with Boundaryless app.

Quest Link Version Mismatch

Yemen

App frame rate drop

Meta Quest 3 first update fails – looking for official OTA / manual update solution

USB: Input-Only Microphone Should Not Mute Built-in Speakers, Technical Analysis & Proposed Fix