Feature request: Custom OAuth state

[anderspitman]

I need to store some extra information alongside the InternalStateData. In order to do this I need access to the oauth state in order to store/retrieve my data. I see two ways this could be implemented:

1. Allow the state parameter to be overridden. This would be a very small change, as it appears the API is already set up for this. This should not break the current API. I would be happy to submit a PR for this.
2. Instead of returning a String from client.authorize(), return a struct that contains the redirect URI and the internally generated state. This might be a more robust solution, but would also break the current API.

Are you open to this functionality?

[sugyan]

I don't understand in what context and what kind of data you want to keep, but I believe that the oauth-client stores/retrieves only the data necessary for authentication, and the user data is stored by the application implementer themself.

The official TypeScript SDK for atproto allows the user to specify a state when calling authorize() and returns the value of that state upon successful callback.
https://github.com/bluesky-social/atproto/tree/main/packages/oauth/oauth-client#authentication
I plan to implement that functionality in ATrium as well, but wouldn't using that state value to store data in the application implementer's own store be a solution?

[anderspitman]

Sorry if I was confusing. I just need exactly the functionality the official SDK provides. If you implement that I should be good to go. In fact I can submit a PR if you'd like.