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").
Our Personal Data Server from scratch!
tranquil.farm
pds
rust
database
fun
oauth
atproto
DPoP bug report #12
open
opened by
launchpadx.top
launchpadx.top
(author)
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
launchpadx.top
(author)
These APIs have same issue too:
xrpc/_delegation.listControllersxrpc/_delegation.listControlledAccountsxrpc/_delegation.getAuditLogxrpc/_backup.exportBlobs
probably there will be more APIs have this issue
launchpadx.top
(author)
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
launchpadx.top
(author)
yep
I can found DPoP request header but the issue is still there
@launchpadx.top is this still affecting you on the latest version?
launchpadx.top
(author)
idk looks like a lot of things like configuration has changed; i recent very busy working on a company project, and when im free i will give it a try
ok lemme know :P
launchpadx.top
(author)
just upgraded to the latest version and this is fixed (i have closed this issue too)
yippieeee
Damn! For which clients is this happening, and which API endpoints specifically???