Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shared config object #34

Open
DavidKrpt opened this issue Apr 25, 2022 · 3 comments
Open

Shared config object #34

DavidKrpt opened this issue Apr 25, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@DavidKrpt
Copy link

Hi, thanks for the package!
I have an app that works the following way: people trust me with their api keys and secrets, I add them to my app, the app makes api calls using their api credentials. Since the app makes calls on behalf of multiple different users, the shared config object becomes an issue. I have to be extra careful to not have simultaneous api calls with different user configs, because I'm afraid when calling init for request B while request A hasn't been sent yet, request A will use request B config. Can you please confirm that this sort of error is in fact possible during simultaneous requests ? If yes, is it possible to initiate multiple instances, each with their own config ?

@saraleung
Copy link

saraleung commented Oct 14, 2022

I upvote this question. I'm in a similar situation. Is OAuth 2.0's Authorization Code Flow supported? Or will it be supported?

@harrydema
Copy link

How did you solve this?

@DavidKrpt
Copy link
Author

@harrydema, hi, unfortunately the app was abandoned before I had the chance to solve anything

@ISAAC-XXYYZZ ISAAC-XXYYZZ self-assigned this Aug 13, 2024
@ISAAC-XXYYZZ ISAAC-XXYYZZ added the enhancement New feature or request label Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants