Skip to content

Config parameter customHeaders is not taken into account #734

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

Closed
jfschaff opened this issue Jun 2, 2022 · 2 comments
Closed

Config parameter customHeaders is not taken into account #734

jfschaff opened this issue Jun 2, 2022 · 2 comments

Comments

@jfschaff
Copy link

jfschaff commented Jun 2, 2022

Issue

It looks like the config parameter customHeaders is disregarded.

const config = {
  ...
  customHeaders: {
    authorize: {
      "X-MyCustomHeader": "value",
    },
  },
};

authorize(config)

The outgoing authorization request does not have a custom header X-MyCustomHeader on Android.


Environment

  • Your Identity Provider: not relevant
  • Platform that you're experiencing the issue on: Android
  • Are you using Expo? No
el173 added a commit to el173/react-native-app-auth that referenced this issue Sep 13, 2022
As per the documentation android custom Headers should pass as `customHeaders` but in module it was accessed as `headers`
@Geraldojrcg
Copy link

I have the same problem in IOS version. Any suggestion?

const config = {
  ...
  additionalHeaders: {
     "X-MyCustomHeader": "value",
  },
};

@carbonrobot
Copy link
Contributor

carbonrobot commented May 2, 2024

The above PR was merged, so I'm closing this for now. If we still have an issue, please reopen.

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

Successfully merging a pull request may close this issue.

3 participants