How to setup many applications using many HTTPs endpoints for HttpSysCommunicationListener

[ConX-Ryan]

Hi Team,

Can I please request documentation and a supporting sample of how to setup many applications using many HTTPs endpoints for HttpSysCommunicationListener (and i guess KestrelCommunicationListener) where the following scenarios are covered.

• n apps using common certificate
• n apps using n certificates

Included in this document I would like to detail the advised strategy to paramerterize endpoints for staging and production environments given they would use different certs in each environment, such that my CI/CD process and source branches play nicely.

I am currently using .bat files to manually configure urlacls etc and I am hoping you can tell me im doing it wrong here is the better way... looking forward to SF mesh so i dont care anymore but until then :)

Thanks for your time, keep up the good work team !!

[dkkapur]

@vturecek

[vturecek]

http.sys supports SNI and looks like Kestrel does too as of asp.net core 2.1 aspnet/KestrelHttpServer#2357. This is going to be the easiest path as you'll only need to include one certificate, which can be set up fairly easily in ApplicationManifest.xml: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-service-manifest-resources#example-specifying-an-https-endpoint-for-your-service

For Kestrel though you'll need to use unique ports for each application as it doesn't support sharing.

[ConX-Ryan]

Trying to replace the .UseHttpSys with .UseWebListener neither seem to have the same SNI config available? the .ListenAnyIP() calls aren't there or I am missing Libraries?

[ConX-Ryan]

So Im being recommended Azure Application Gateway by support ... I would really like to see the SF team own this kind of deployment and document recommendations better please