Support setting X-Forwarded-* headers

[bdemers]

Based on comments from #13 and #14 from @mfulgo

Setting a X-Forwarded-For header is required for this scenario.

(comments welcome)

[bdemers]

@mfulgo Let's chat about this use case a little more on this issue.

How much are you tweaking the response bodies when proxying the requests? Is it a straight proxy, or are you supporting a migration scenario ?

[mfulgo]

It's not a straight proxy: I'm expecting to drop the links and some other fields from the responses, as I expect the client application to know and follow a certain flow, and I don't want to expose the Okta endpoint URL.

I also need to do some custom validation of phone numbers used for SMS factors, which is one of the primary reasons for doing the proxy.

[bdemers]

Thanks! that helps!

[jmalickenexient]

Any update here? I've looked through the docs and library and sadly it looks like I'd have to hack the inner-guts to send a X-Forwarded-* header (which is not easily feasible and comes with a host of its own problems). Appreciate your hard work on this library and any updates you have to share.

[bdemers]

Nothing yet, what are you currently doing? maybe we can provide another option?

[mfulgo]

Thanks, @bdemers!

[jmalickenexient]

Thank you @bdemers !!