Override the ClaimsToHeadersMiddleware by the OcelotPipelineConfiguration settings

[kesskalli]

New Feature

The idea is to allow to use custom claims to headers transformation logic after the authorization process is done.
The transformation using a JSON file requires to handle everything by route. The file will become very verbose in this case.
In some cases, the internal HTTP services can expect some HTTP "X-" Headers to get more context about the request (to support multi-tenancy for instance), the override will allow to add them automatically.

Proposed Changes

• Allowed to override the ClaimsToHeaders middleware
• The override can be "injected" in the Ocelot config on start-up

[raman-m]

@kesskalli Hi Karim!
Thanks for the great idea and PR!

3 years have been passed...
Do you have an intention to contribute nowadays?

[raman-m]

The changes are not covered by unit and acceptance tests!
Let's collaborate on writing tests...

[raman-m]

@kesskalli Hi Karim!
The feature branch has been rebased onto ThreeMammals:develop successfully!

---

I see that develop branch in your fork is old!
Could you Sync fork please? So, the develop branch will be updated with all top commits!
Could you add me as collaborator to your forked repo please? I will update develop branch.

[raman-m]

@kesskalli commented on Dec 28, 2020:

Proposed Changes

• Allowed to override the ClaimsToHeaders middleware

I see these changes. The community will review them soon.

---

• The override can be "injected" in the Ocelot config on start-up

Yeah, but in theory. And I don't see these changes in files.
It would be a good idea to add a sample web app to demonstrate how to override this middleware.

---

Also, don't forget to write tests please!

---

Is this PR related to an issue in backlog?