Let’s first finish E2E. The placeholders thing is a crappy solution (imho) and a virtual filesystem means re-implementing 90% of the client… But it is the right way to go.
Please test the RC and submit a bug report in github pls!
I would start testing if they would provide HTTP/2 for the client.
Does it now support Windows AD SSO?
E2E still doesn’t work with nginx. My github issue is still open I believe.
Link? There’s no reason it shouldn’t work, at least from the client side. Could be a server issue, though.
In theory, anything that works in the server works in the client thanks to our new login flow. Try it out to be sure and report back please 
Well, I don’t know if it works now or is supposed to work. Why not give it a try and let us know? I don’t think this will get muc priority unless we know it doesn’t work 
and even then it does of course also depend on demand, customer requirements and volunteers who want to work on it. Your help is welcome!
It does work with my setup (NC 14.0.3 + Apache + HTTP/2) 
2 Likes
It worked in versions from several months ago. I can’t tell you the exact time it stopped working, but it was quite a few months ago.
Where can I officially report back bugs / observations I made?
Updated to this RC1 build, no more problem with the HANG at Redirecting. But still with an old version of OpenSSL.
It’s not actually an old version of OpenSSL. It doesn’t show the actual version being used. The old version is included as well, but it’s not active/compiled with it.
1 Like
any chance you could test with the 2nd RC? And reply in the issue? It might qualify as release blocker though that’s a decision for the devs, not me.
I’ll give it a shot. IMHO, it should be a release blocker, as if you are using the client and have E2E enabled on the server, it won’t work at all. (if you use nginx)
Still broken.
See the release blog 
we’re already working on a 2.5.1!