I think we’re all good to go on this, so thanks for all your help Joel! Here’s the link to the public project that we’re going to be embedding on our website: https://met.norcalcontrols.net/
Awesome - what was the root cause of the last issue? (the infinite redirect issue)
Did you simply leave all of the settings disabled (as mentioned in your second-to-last post)? (if that’s the case, I’m wondering how your cross-origin iframe is working…unless you abandoned that approach?)
This was happening when I visited the gateway directly, not through any proxy or embed. The infinite redirect was triggering anytime I went to login to the gateway through my IDP. The IDP was an ignition internal IDP. I required IDP authentication to do anything on the gw webpage, including viewing the home tab, but for some reason when those settings are enabled, I can’t even go through authentication as the page keeps redirecting to itself over and over until TOO_MANY_REDIRECTS is thrown. Disabling those settings worked, and once I disabled them I added a new certificate to the gateway and then re-enabled them. I’m not sure if that clears anything up though. If I could hazard a guess, maybe the servlet that provides that page keeps appending the Location header and returning 302 if those flags are set in ignition.conf, except since there’s no secure IDP route once you disable SSL, it defaults to using the insecure route instead?
huh, weird. were there any seemingly related exceptions in the gateway logs when this issue occurs? and is this issue still happening after installing the new cert and re-enabling (un-commenting) those settings?
if the issue was only temporary, we have seen this before when navigating to the Gateway using both http and https URLs, which causes conflicts with the session cookies, since session cookies in https requests will have a secure flag set on them, and browsers will refuse to send the cookie over http until the browser is closed / cookies and cache are cleared. A similar dynamic can happen when installing a new web server new SSL cert.
Before I disabled the settings, nothing I tried was working to let me into the gateway. I tried clearing cache and deleting cookies several times, with no resolution. I was effectively locked out because login attempts kept redirecting in a loop. If I re-enabled the settings, the issue came back, and then adding the certificate and re-enabling the settings caused it to no longer happen. This leads me to believe that it might have been related to those settings, but I can’t say for sure. I cross-referenced the time I was locked out in the logs, and I didn’t find anything relevant unfortunately.
Ok, thanks for the info / checking the logs.