wso2 / wso2/docs-apim

Add relevant configs of way to Preserve/Override the Authorization header in the Micro-gateway

Open
#3,185 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

CEXP Severity/Minor Type/Bug
Dominant language
CSS
Stars
99
Forks
708
Avg merge
1d 7h
Merged PRs (30d)
22

Description

Description:
To send the same "Authorization" header from the initial request to the back end api. if we want the original request header used for Authorization to be passed through the micro-gateway to the back-end service as require information from the JWT token on the web service  and if don't want to use different header values for this between WSO2 and the back end service.
We cant use the configuration which is mentioned in documentation[1].

In order to achieve that we have use the below configuration.

[authConfig]
  # Authorization header expected by the Micro-gateway. Can be overridden at API level using the extension
  authorizationHeader = "Authorization"
  # Remove authorization header from the backend request
  removeAuthHeaderFromOutMessage = false  

But those details were not there in the documentation[1]. Those details need to be included to the documentation[1].

Suggested Labels:

Micro-gateway-3.2.0

[1] https://mg.docs.wso2.com/en/latest/how-tos/preserve-override-headers/

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open the linked preserve/override headers documentation page and compare it with the [authConfig] settings shown in the issue. Document authorizationHeader and removeAuthHeaderFromOutMessage, including how they preserve or remove the Authorization header. Done means the page explains these settings accurately and the configuration example is clear.

Written by the indexing model from the issue text.

Assessment

Domain
api, documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.