Hello,
I'm having trouble getting vnext, web classic, REST API, and M-Files Mobiles to work at the same time.
I'm using the option "Set up M-Files Web, classic M-Files Web (enabled), M-Files REST API, and M-Files Mobile"
Then "Create a new website" with default values : Name M-Files, Port 80
Site Binding Address http://127.0.0.1:80
No proxy
"Use M-Files Web as default web client on this server" disabled
On IIS, new binding on https added with SSL certificate
Access to vnext works (mfiles.mydomain.local/vnext)
is it possible to enable Windows SSO for vnext ?
Access to classic web not working (mfiles.mydomain.local/login.asxp redirected to mfiles.mydomain.local/WindowsLogin.aspx)
The Web Browser keep prompting for password (Windows Security Window)
Windows Authentication is enabled on IIS
If I disable the URL rewrite rule "ReverseProxyInboundRule_vNext", Classic Web works but not the vnext ofc
- Pattern : (.*)
- Conditions (all conditions) :
- {HTTP_X_MFPROXY_PROCESSED} : ^$
- {REQUEST_URI} : ^/(?!rpc/|rpcwithcert/|rest/|m/|webhook/|windowslogin.aspx/|webservicesso.aspx).*$
- Server variables :
- HTTP_X_FORWARDED_PROTO : {MapProtocol:{HTTPS}}
- HTTP_X_FORWARDED_HOST : {HTTP_HOST}
Maybe Windows SSO is not compatible with the classic web when VNEXT is enabled
I tried to disable Windows SSO can't access URI Configuration.aspx : TOO_MANY_REDIRECTS
Thank you for your help
