Hi,
Nginx was just an example - the overall point was that you need to make sure that the HTTPS protocol scheme is being maintained throughout the entire redirect chain. However, given some of the error messages you're receiving below, I'm not sure that's actually what is going on.
I think for SAML if you set |SAML_STRICT| to |false| (docker/podman environment variable) or |saml-strict| (configuration file) to |false| it should also work if not the entire chain is https. That happened to me when using SAML behind nginx to a local container.
As Nick already pointed out you should enable debugging to get more detailled information to find out what the error is related to.
(set |LOGBACK_LEVEL/logback-level| to |debug|) Regards Peter ​
