Hello folks, I notice the latest install guide for EMWW on EpicWeb is 2021.1, and it still says net.tcp binding with UsernameWindowsChannel is required.
That’s great from an upgrade point of view, but in the 2022.1 Kinetic upgrade the speak very firmly about not using net.tcp
Anyone know any more than that?
Welp, finally got here and it works with https. You have to set Windows auth and “Allow Windows”, not Basic and allow.
There’s a tricky bit if your server does NOT have a public DNS record, because you still have to have a cert and in this case it’s self signed. In other words, you devices are all inside your walls and only working over LAN.
On 10.2.700 we just used machine name/appserver but now you have to use https://machine name/appserver and it simply fails invisibly. Luckily in the EMWW user guide I happened on a section for using self-cert. You just have to open chrome, go to https://machine name/appserver/api/help and allow chrome to go to the “unsafe” location, and then log in to the REST help page with the domain user assigned to your device.
In our case a very minor pain because we disable chrome on these things, but it works.
try going to your browser and logging into the homepage with an incorrect password for this app server that you have set up now with allow windows. Do you get a windows credential pop up?
This has nothing to do with EMWW btw… just wanted you to know that you’ll be faced with another “minor” pain when you enter an incorrect password.
actually, I re-disabled chrome, and everything continues to work. We’re using LDAP windows auth, not Azure. So the only cred request we’re getting is the EMWW and it doesn’t fail gracefully - enter a wrong password and it just stares back at you like Paddington
*edit - well, not EVERYTHING works - there’s another issue probably not related but I’ll start another topic