Fix the "double /pipeline/ load", while logging in via IdP, caused by EDGE ingress redirections
return 301 ${CP_DOLLAR}scheme://${CP_DOLLAR}host/pipeline/;
}
+ # Fixes the issue with the "double /pipeline/ load", while logging in, i.e.:
+ # - User logins for the first time
+ # - The user is redirected to /pipeline/saml/login
+ # - This causes two requests:
+ # -- Redirect to the IdP endpoint
+ # -- Web-browser performs request to /favicon.ico, which is handled by the above section (location /)
+ # - As a result - user is redirected back to /pipeline and a second authenication attempt is performed
+ location /favicon.ico {
+ return 301 $scheme://$host/pipeline/favicon.png;
+ }
+
location /pipeline/ {
# see ../nginx.conf for comments on the resolver usage
resolver ${CP_EDGE_CLUSTER_RESOLVER} valid=${CP_EDGE_CLUSTER_RESOLVER_TIMEOUT_SEC}s ipv6=off;
