I'm very interested in combining BrowZer with our on-prem Exchange server. IMO Exchange has a questionable history of security issues and using BrowZer to decouple it from the internet is a compelling idea.
I've got my OpenZiti overlay working. I believe I've got BrowZer working too. The bootstrapper starts, I login to the auth provider, and eventually I'm shown the login page for OWA. But the login process just loops. Put in password, click login, back to login page again.
I compared the network activity from a good (no browzer) login vs a browzer login. There's supposed to be a POST that returns a bunch of cookies. Those cookies are present in the next request which eventually loads the mailbox. In the browzer session the cookies don't come through and are absent on the following request.
I confirmed that OWA doesn't seem to care which FQDN I use to reach it. I setup a hosts file entry and ran a test w/o browzer. Works fine. It doesn't seem to mind being behind a reverse proxy.
Any thoughts or suggestions on how to debug this further or tweak browzer?
Thanks for trying out browZer with your private Exchange/OWA. I'm excited you're doing this because this use case is one on our list that we haven't gotten to yet.
Which version of browZer are you running right now?
If you are willing, here are some suggestions that will help me troubleshoot (via private msgs):
Set your client-side trace level to TRACE (set env var ZITI_BROWZER_RUNTIME_LOGLEVEL=trace in bootstrapper), then open dev tools, go through the failing flow, then save the Console log and send it to me, and save the Network har file and send that to me.
OK, you have the latest. I recently fixed a similar Cookie issue to what you described (in 0.60.2), so wanted to make sure you had that fix.
Also, see my "private Discourse chat" msg to you.
browzer-cookie.txt (58.0 KB)
Hello curt, I have a local service called zentao. You can search for this open source project on github. Currently, direct access is fine. You can access the login page through the browzer, but you cannot jump after entering the account and password and clicking login. This is my browzer trace record. I compared their interfaces and found that the cookie was not carried when the browzer accessed
I have reproduced the issue, and I see the problem. ZBR is doing an inappropriate transformation on the HTML returned from the request to ZenTao's /index.php?m=user&f=refreshRandom endpoint, which leads to bogus data being sent in the form data on the subsequent request to /index.php?m=user&f=login. I am working on a fix now.
I changed to another test service and it can be accessed, but the situation is the same as the previous zentao, it cannot carry cookies and cannot jump
