I do not know how to modify X-Forwarded-Proto to https, without terminating at the Ingress controller.
Currently the LB is setting the right headers i.e. X-Forwarded-Proto: http. And the intention is to connect to FA over http.
But because browser shows https, and doesn't matches with the origin, CSRF doesn't gets satisfied
Posts made by faisal.jamil
RE: Proxy Warning with NLB before Ingress
Proxy Warning with NLB before Ingress
We've installed FA on a kubernetes cluster. Ingress resource is setup to get connection over http. We know that by default, TLS is terminated in the ingress controller. But we've configured it to terminate TLS in the Load Balancer. Load balancer is an AWS NLB used from https://kubernetes.github.io/ingress-nginx/deploy/#aws
We are getting the following warning, that makes total sense.
The question is how to get around this warning, and add a X-forwarded-proto header to our Ingress controller but talk over http. Please Note: We do not want to terminate TLS on Ingress controller because then we cannot get AWS Certificate Manager to renew certificates automatically.
Any help or hints to move forward would be highly appreciated.
SMS send limit
We are using MFA APIs from Fusionauth Developer Edition, and using SMS as auth factor. We are able to send out SMSs, and use it for our 2FA needs, but
- We are unable to find, if there is a limit to send out SMSs in dev or production environments?
- Do we need to buy an additional subscription for our MFA needs from a service like Twillio?