Our Personal Data Server from scratch! tranquil.farm
oauth atproto pds rust postgresql objectstorage fun

DPoP bug report #11

open opened by launchpadx.top

I've observed that since the recent update (starting from 8af0cfe0), some API requests (e.g., oauth/sso/linked) have encountered a "use_dpop_nonce" error (the message is "DPoP nonce required").

Damn! For which clients is this happening, and which API endpoints specifically???

I haven't encountered any issues currently with the Bluesky client, this problem looks like only exists with PDS Account Manager.

Looks like a lot APIs are experiencing this issue, including the one I mentioned in the issue, as well as a new API (com.atproto.server.getSession) I just discovered that also has this problem

These APIs have same issue too:

  • xrpc/_delegation.listControllers
  • xrpc/_delegation.listControlledAccounts
  • xrpc/_delegation.getAuditLog
  • xrpc/_backup.exportBlobs

probably there will be more APIs have this issue

i'll hopefully look at this and fix within a week

Looks like this issue is not resolved completely, as /oauth/sso/linked still have problem, error is invalid_dpop_proof and message is HTTP URI mismatch

you definitely rebuilt the frontend code right? :3

yep

I can found DPoP request header but the issue is still there

sign up or login to add to the discussion
Labels

None yet.

assignee

None yet.

Participants 2
AT URI
at://did:plc:gcktt4t6eocohmc2f4rozxly/sh.tangled.repo.issue/3mdb3heakvi22