feat: add request header in match context

[msumit]

Related issue

#512

Proposed changes

After wasting a lot of time on why I'm not able to use Headers within the Remote Authorizer, I found out that Oathkeeper isn't setting the Headers while initializing the AuthenticationSession. We use Remote Authorizer and pass on some key information through headers only & without this fix, we can't use Oathkeeper at all, so setting the request headers inside MatchContext.

Checklist

• I have read the contributing guidelines.
• I have read the security policy.
• I confirm that this pull request does not address a security
  vulnerability. If this pull request addresses a security. vulnerability, I
  confirm that I got green light (please contact
  [email protected]) from the maintainers to push
  the changes.
• I have added tests that prove my fix is effective or that my feature
  works.
• I have added or changed the documentation.

Further comments

See this PR -> #718

[andriisoldatenko]

i think for expected results better to use constant / or literal instead of function

[msumit]

@aeneasr can you plz review.

[aeneasr]

Thank you this looks great and sorry for the late review - last week was hectic :)

Could you please also update the documentation in docs/docs on this? Thank you!

[aeneasr]

Thank you, this looks great! The CI is failing because some files are formatted incorrectly. To format them, run:

$ make format
$ git commit -a -m "styles: format code"
$ git push

Thank you!

[aeneasr]

Hmmm...why isn't the pipeline triggering -.-

[msumit]

@aeneasr can you figure out why the windows go test is failing?

[aeneasr]

Yeah it's not your fault!

[aeneasr]

But ci/circleci: test should be running and it's not :/ I have one guide regarding this:

---

Unfortunately, for some reason, the CircleCI tests are not running. Do you maybe follow your/a fork of this repository on CircleCI? If so, you need to unsubscribe / unwatch from that CircleCI project. Then, make another push to your branch using:

$ git commit --amend --allow-empty
$ git push --force

That should get the CI running! Thank you :)

[msumit]

@aeneasr I think you need to approve something somewhere to kick off the tests.
First-time contributors need a maintainer to approve running workflows. Learn more.

[msumit]

@aeneasr can you look into this

[aeneasr]

Hey there, sorry for the long delay - yesterday was a holiday :) I've approved the run. I've also create a post on GH community regarding this as the current approval behavior is so annoying.

[aeneasr]

Hm no, this looks like a circle ci issue. I'll run the tests locally

[aeneasr]

Awesome, thank you! 🎉 Your contribution makes Ory better :)