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
httpOptions
missing on OAuth config in experimental version
#8491
Comments
Can you add a more concrete example? N/A is not a valid reproduction. 🤷♂️ Even if it's a feature request, it would be good to understand the reason. |
Usage on 4.x Keycloak({
// ...
httpOptions: {
headers: {
'some-header-name': 'some-header-value'
}
}
}), Usage on 5.x As for the reasoning and use-case: there could be all sorts. One concrete example for custom header support would be if the authorization server is behind a security proxy and requires a service token or other authorization header(s). Of course there are other ways of addressing this scenario with varying levels of complexity, but using headers was a very simple & effective way to get going. Let me know if there's anything else I can provide. |
This is a blocker for my app and v5 as well. Another use case, setting a custom agent in
|
This will be a blocker for us as well unfortunately from upgrading - our use case is similar in that we require additional httpHeaders on the requests made to our OAuth provider |
|
I am facing this similar issue. I can not extend the timeout during debugging. Can we please have this back? Or another way of doing this? |
same as @bujikun, missing the |
Description 📓
We have been using the
httpOptions
parameter in next-auth's 4.xOAuthConfig
to set a header we require for our IDP.I noticed this is missing in @auth/core's
OAuth2Config
, and unfortunately will be a blocker/headache for us to upgrade.It seems the 'oauth4webapi' library supports additional headers.
How to reproduce ☕️
N/A
Contributing 🙌🏽
Yes, I am willing to help implement this feature in a PR
The text was updated successfully, but these errors were encountered: