Please or Register to create posts and topics.

Unable to Login

I have published my app in IIS and I can get to home page no problem. As soon as I try to log in I get this message:


issuer must use HTTPS (with TLS), or config value for property 'requireHttps' must be set to 'false' and allow HTTP (without TLS).

I have tried all kinds of settings to make this go away and I cannot. I do not need SSL for this app because it is being served via  a reverse proxy through a DMZ.

Please help!!!! I really like this app and need to get past this so I can finish building out this site.


Thank you

Come on Eben!! I paid for the version I have and it is supposed to come with support. 

You can't be selling something and then not support it!!

I really need help disabling SSL!

Hello David,

Sorry for the late response.
To disable SSL comment out this line app.UseHsts(); in Startup.cs
More information on HSTS here: https://aka.ms/aspnetcore-hsts

Also delete the entries "https_port" or "sslPort" from:

Note that you might have to clear hsts settings for the web app if your browser has already cached the HSTS headers.
Google "clear hsts in browser" for your specific browser on how to do this.

Let me know if there's anything else I can be of help with.


[Eben Monney]

Thank you for responding! I appreciate that.

I have done as instructed above and I am still getting the error. I also did the following:

Comment out - app.UseHttpsRedirection()

added - requireHttps : false - to environment.prod.ts

But I still get the error:

Severity: "error", Summary: "Unable to login", Detail: "issuer must use HTTPS (with TLS), or config value for property 'requireHttps' must be set to 'false' and allow HTTP (without TLS).", Error: ""issuer must use HTTPS (with TLS), or config value for property 'requireHttps' must be set to 'false' and allow HTTP (without TLS)."" logError @ main.2b3812467de2b9582eef.js:1

Am I not setting the requireHttps property in the right place?

**Quick note: everything works fine when running in Visual Studio, I get this error after publishing to IIS. IIS is set up to run just http***

Thank you!

Uploaded files:
  • quickApp-error.PNG

Hello David,

Your application is successfully using http and not https.
What is happening is angular-oauth2-oidc does not allow http on anything other than localhost by default. So you'll need to fix that.

From oidc-helper.service.ts add the below line to the constructor or the appropriate method.

     requireHttps: false


[Eben Monney]

I'm getting closer!!!! Thank you!!

Have an additional issue. I got the error "The target resource cannot be found. http://proxy.internalbaldwinshell.net/.well-known/openid-configuration". I am not getting a json response when I navigate to this address. Gives me a 404 not found.

After Googling for a while and finding a few suggestions I did a URL Rewrite rule in a web.config.  That took care of the problem of not finding /.well-known/openid-configuration but now I am getting this error "UNABLE TO LOGIN SyntaxError: Unexpected token < in JSON at position 0"

Upon further investigation it still seems like it's not getting the /.well-known/openid-configuration though. The response is the html from index.html in the src folder, not a json response.

Once again, any help would be greatly appreciated.   While do have the skills to add additional content to your SPA, I do not have your skills and knowledge to build what you have created and I am very excited and ready to use it. The openid, login, authentication, etc is what I am really not skilled in and need help with.

At this point if I am asking to much I would be more than happy to do a remote session and pay. I really need this application up an running.

Thank you!!


the rewrite code:

<rule name="Angular Routes" stopProcessing="true">
<match url=".*" />
<conditions logicalGrouping="MatchAll">
<add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
<add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" />
<action type="Rewrite" url="/" />

Uploaded files:
  • quickApp-error-2.PNG


It appears IdentifyServer is blocking your connection on http.
What do the logs say? \Logs

Note that openid communication on http is not standard practice outside of localhost.
Consider using the Forwarded Headers Middleware:



NO you're not asking for too much. It's a pleasure to help where I can.
Share your logs on support@ebenmonney.com and let's have a look.
You can share it here too if you're confident it doesn't contain personal information

[Eben Monney]