如何使用带有https而不是localhost的域名在IIS中调试网站

Question

I am implementing Single Sign On(using OKTA) on one of our MVC based website where the OKTA takes a Response URL to throw its response back to my code once the user has entered his credentials on OKTA login page

OKTA takes an based response URL to throw its response.

Things I have done:

1) I have specified a dummy Hostname to my machine using file like:

127.0.0.1 www.abc.com

2) Enabled on www.abc.com on my local machine

3) Specified a route {{controller}}/{{Action}} to receive the response in my code.

4) I have tried specifying Bindings to my local applicationConf file:

             <bindings>
                <binding protocol="http" bindingInformation="*:58565:localhost" />
                  <binding protocol="https" bindingInformation="*:443:www.abc.com" />
            </bindings>

My VS project configuration looks like this:

Is it possible to receive the response on the local MVC route (hit the breakpoint) when the URL (where OKTA throws response) is like

when I write or with VS debugging on, it hits the breakpoint but when I type (with https) it does not hit the breakpoint in Visual Studio. With https it says 404 Not found.

Am I missing something?

Thanks

Answer 1

I got the issue fixed. Posting the solution so that it may be helpful for others.

Steps I followed:

1) Created a Self signed certificate with Powershell(make sure you run Powershell command line with Admin Privileges)

New-SelfSignedCertificate -DnsName www.mydomain.com -CertStoreLocation cert:\LocalMachine\My

2) Have correct bindings in my ApplicationConf.host file(this file is now at Project level now since VS 2015 rather than at IIS level) like the one below:

        <bindings>
                <binding protocol="http" bindingInformation="*:58565:localhost" />
                <binding protocol="https" bindingInformation="*:44311:localhost" />
       </bindings>

You can add more bindings if using Hostname instead of Localhost. Make sure ports are different for each binding. Also, Https ports should start from 443--ending at 44399.

3) Remove the existing https binding from IIS Default Website and add it back with the certificate created in Step 1 and correct hostname used in Step 1.

Now you should be able to run and debug your code on local machine with self signed SSL.