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

NextRequest auth handling #182

Open
stucka opened this issue Dec 27, 2024 · 1 comment
Open

NextRequest auth handling #182

stucka opened this issue Dec 27, 2024 · 1 comment
Assignees

Comments

@stucka
Copy link
Contributor

stucka commented Dec 27, 2024

Additional details

This has been needed for some weeks but was never made into an issue.

NextRequest should handle authentication. I think maybe the way forward is to start the login as a session in requests, then pass that auth info in as an optional flag to latter NextRequest library functions, and from there store as maybe a bln_auth subkey(s) within the metadata. It's possible we may need to track for type of request (POST, GET), request headers and possibly payload.

Related pull request(s)

  • #00
@stucka stucka self-assigned this Dec 27, 2024
@stucka
Copy link
Contributor Author

stucka commented Jan 19, 2025

Need to fold in actual auth data into returned JSON.

Possibly a race condition on auth problems? Consider auth steps with waiting (2*throttle)+2 seconds.

Are headers handled separately from cookies? Could that be part of the problem?

stucka added a commit that referenced this issue Feb 6, 2025
* Initial auth run

* Extra testing stuff, but at least one fix

* NextRequest and Mendo SO production

* Update contributors list

* Document auth metadata
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant