It would appear the issue is the request for the openid scope. Guess we'll see if we can work around it. -- Tom Strickx Principal Network Engineer AS13335 - Cloudflare
On Mon, Mar 2, 2026 at 3:30 PM Tom Strickx <[email protected]> wrote: > To follow up on this: > If we move the client_id+client_secret into the Authorization header, we > seem to bypass the 500, but now end up with: > {"body":{"meta":{"error":"Invalid username or password"}}}} > > This also seems suboptimal, especially since I know the credentials used > are correct. > -- > Tom Strickx > Principal Network Engineer > AS13335 - Cloudflare > > > On Mon, Mar 2, 2026 at 2:33 PM Tom Strickx <[email protected]> > wrote: > >> Hey, >> >> Since the upgrade, our (peering.cloudflare.com) PeeringDB integration >> broke. >> Specifically, it looks like we're getting 500s now from >> https://auth.peeringdb.com/oauth2/token/ >> >> We do a POST to that endpoint with the following: >> >> redirect_uri: "https://net.cloudflareaccess.com/cdn-cgi/access/callback"; >> code: ... >> grant_type: 'authorization_code' >> client_id: ... >> client_secret: ... >> >> We're not too sure what changed, given this used to work, and we haven't >> touched anything on our end. >> >> Does anyone have any idea what could be going on? Or, ideally, someone who >> can look at the backend and tell us what's dying? >> >> Any and all insights appreciated >> >> -- >> Tom Strickx >> Principal Network Engineer >> AS13335 - Cloudflare >> >
_______________________________________________ Pdb-tech mailing list [email protected] https://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-tech
