To trust .NET self signed SSL certificates, perform the following one-time step. Close all your browsers and open command prompt, write:
dotnet dev-certs https --trust
This will allow to trust the self-signed ASP NET Core HTTPS development certificate in your computer.
A confirmation prompt will be displayed if the certificate was not previously trusted. Click yes
on the prompt to trust the certificate.
If you want to clear your existing HTTPS certificates. Open command prompt, write:
dotnet dev-certs https –clean
Google Chrome uses the
Certificate Store
on Windows for validating certificates, therefore when you run the command, Chrome will not complain about the certificate anymore!
References:
hi,
how do you build for production?
The package Volo.Abp.AspNetCore.Mvc.UI.Theme.Shared
is on NuGet .
It should find it from https://www.nuget.org/packages/Volo.Abp.AspNetCore.Mvc.UI.Theme.Shared/
Check your NuGet.Config
. The order of the package sources are important.
It should be first "nuget.org" then "ABP Commercial NuGet Source"
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
<add key="ABP Commercial NuGet Source" value="https://nuget.abp.io/*************/v3/index.json" />
</packageSources>
</configuration>
Don't forget to replace your private API Key (/*************/)
this issue has been fixed in v2.4 (coming on April 3, 2020)
hi,
we'll try to reproduce and get back to you
Firefox has an optional feature that allows the browser to trust root authorities in the Windows certificate store. To activate this feature, you must enable the setting in your browser.
about:config
into the Firefox address bar.
security.enterprise_roots.enabled
security.enterprise_roots.enabled
window, look to the right side of the screen. If the value is false
, double-click on it to set it as true
.try signing in from http://localhost:4200/account/login then you'll see the administrator menu.
I think the problem is there's no Login link.