You are viewing limited content. For full access, please sign in.

Question

Question

reverse proxy

asked on December 4, 2020

OK, I had the reverse proxy setup and functional on my DMZ server (Thank you Samuel)

A few weeks ago, we installed Laserfiche Directory Server to remedy issues with participant licenses not being able to be assigned. Since then, and attempt to access forms from an outside URL produces a too many redirects error.

The server name hasn't changed.

If I set the inbound rule to redirect instead of rewrite, I will get the form to load but it shows the URL to my inside server in the address bar instead of the internet URL, but at least i know the DMZ server is still hitting the Web Portal server.

I am able to access the forms using a URL to the web Portal server from inside the network using the same server name that the Reverse Proxy setup has for the inbound rewrite.

Still scratching my head.

Any ideas are welcome.

Thanks - Eric

0 0

Answer

APPROVED ANSWER SELECTED ANSWER
replied on December 10, 2020 Show version history

To close the loop here, the issue was the proxy was performing SSL termination and sending plain HTTP requests to the backend. Once LFDS is configured as the user authentication source for Forms, Forms requires HTTPS for all requests (even if they are to a public Form that does not require authentication, because it is a global setting). HTTPS redirection is not sufficient because the proxy doesn't follow redirects the same way a browser does.

Updating the proxy to send HTTPS rather than HTTP requests to Forms along with trusting the Forms server's certificate chain resolved the issue.

3 0

Replies

replied on December 4, 2020

Hey Eric, 

Can you shoot me an email? I probably have time to take a look with you next week.

Cheers, 

Sam

0 0
APPROVED ANSWER SELECTED ANSWER
replied on December 10, 2020 Show version history

To close the loop here, the issue was the proxy was performing SSL termination and sending plain HTTP requests to the backend. Once LFDS is configured as the user authentication source for Forms, Forms requires HTTPS for all requests (even if they are to a public Form that does not require authentication, because it is a global setting). HTTPS redirection is not sufficient because the proxy doesn't follow redirects the same way a browser does.

Updating the proxy to send HTTPS rather than HTTP requests to Forms along with trusting the Forms server's certificate chain resolved the issue.

3 0
You are not allowed to follow up in this post.

Sign in to reply to this post.