@yngve interesting.
Well, in any case, my particular issue got resolved. I think ASP.net did something in the background to setup a cert locally, and it took a moment for that to propagate. A recent run of the swagger page did not trigger any issues.
Thanks for the replies!