Manage X-Forwarded-Port on Gateway

[ppgravitee]

As platform administrator I want to use a reverse proxy in front of the AccessManagement service and be able to specify the listening port of this proxy. As a consequence the AM Gateway have to manage theX-Forwarded-Port header to build the right URL when a redirection has to be done.

Currently, the URL is build using this class : [https://github.com/gravitee-io/gravitee-access-management/blob/master/gravitee-am-gateway/gravitee-am-gateway-handler/gravitee-am-gateway-handler-common/src/main/java/io/gravitee/am/gateway/handler/common/vertx/utils/UriBuilderRequest.java|https://github.com/gravitee-io/gravitee-access-management/blob/master/gravitee-am-gateway/gravitee-am-gateway-handler/gravitee-am-gateway-handler-common/src/main/java/io/gravitee/am/gateway/handler/common/vertx/utils/UriBuilderRequest.java]

h1. How to test:

Use the docker-compose.yml available into the AM project directory docker/compose. Define a custom port for nginx. Try to initiate a login flow, the GW should redirect you on the right login page.

You will need to apply the changes of this PR [https://github.com/gravitee-io/gravitee-access-management/pull/2201|https://github.com/gravitee-io/gravitee-access-management/pull/2201] in 3.15.x to be able to test

[exalate-issue-sync]

Anastasiia Vasylenko commented: Env: [https://am.management.v3-18-x.gravitee.dev/|https://am.management.v3-18-x.gravitee.dev/|smart-link]
Version: 3.18.13

As discussed with Eric - this PR were tested locally