Bug in OAuth process?

[jramseyer]

@TheEnbyperor reports:

"The PeeringDB Auth is woefully underspecified, and maybe even broken. I tried to follow it and made a client_credentials application owned by my organization. When I used the access token to query https://auth.peeringdb.com/profile/v1 this returned a 500 Internal Server Error so this doesn't appear to be the correct way to go about things. The draft talks about OAuth Authorization Code Exchange grant type, but that is (to my understanding) for interactive login sessions with a human present. This draft defines a machine to machine API so the Client Credentials grant type should be used instead."
(copied from #30)

We should investigate to see if client_credentials is no longer working.

[ichdasich]

I just spent a bit of time trying to get this working; So far i had a similar experience to Q, though.

It would be nice to have a sample client in bash and curl around in the repo.