Extra parameters in the server-side authorization process

[gabe....@gmail.com]

Hello All

I have a problem where my app is mostly being built with Angular using an oAuth token to log users in. So there is no session or anything server side to track users. We are using the server side method of authorizing with eventbrite.

In order to authorize, I have to send the user off to EB which sends them back to an endpoint on the api server.

The hangup is that I don't know who is logged in once I am back from the excursion. Some APIs let you add an additional field and it will just post it back to you, so you could send your user id in and then retrieve it back.

I don't see anything in the docs about being able to do this here.

How would one of you solve the problem of being able to link the newly begotten auth token to your user to store it?

[gabe....@gmail.com]

Figured it out. You can add the state=whatever field to your initial redirect and it comes back along with the authorization code.

Why isn't this in the documentation? :<