By using AWS re:Post, you agree to the AWS re:Post Terms of Use

x-forwarded-proto header missing in ALB

0

Hi, Created ALB using ingress controller. Ingress.yaml has all the relevant annotations. Initial flow works fine i.e. browser->https://url->R53->public hosted zone-> public ALB-> service->pod However, when integrate the service with SAML IDP, after successful authentication, SAML assertion fails as returned/redirect url to service is http:// rather than https:// AWS docs mentioned, ALB supports x-forwarded headers but not able to get the client's original protocol as x-forwarded header is missing. Look for help to know how to get x-forwarded-proto header in the request? Any specific annotation to get this? Thanks !!

asked 2 years ago362 views
1 Answer
0

Hello,

There is a feature where you can either remove, append, or preserve x-forwarded header but currently it is only supported for x-forwarded-for and x-forwarded-proto is unaffected. If you are using, authentication feature for SAML authentication, in that case it won't work or your configuration has to be - ALB - auth -> cognito ---> SAML.

[+] HTTP headers and Application Load Balancers - X-Forwarded-For - https://docs.aws.amazon.com/elasticloadbalancing/latest/application/x-forwarded-headers.html#x-forwarded-for

AWS
SUPPORT ENGINEER
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions