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

Client applications should be able to use non-bearer authorization #89

Open
sentient-glare opened this issue Mar 15, 2023 · 0 comments
Open

Comments

@sentient-glare
Copy link

Currently it seems that client applications are forced to have their tokens interpreted as a Bearer token. This causes problems where other authentication schemes are required.

https://github.com/pyroscope-io/pyroscope-rs/blob/23fb2fdc3a7a7f7196f2a7811b90ea1360f4ce7f/src/session.rs#L230
https://docs.rs/reqwest/latest/src/reqwest/async_impl/request.rs.html#261

An option that allows the client to set the entire value of the Authorization header would be the fix for my use case.

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