Activities of "alper"

How to connect ASP NET Core self-signed HTTPS development certificate? [Chrome Fix]

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:

  • https://www.hanselman.com/blog/DevelopingLocallyWithASPNETCoreUnderHTTPSSSLAndSelfSignedCerts.aspx
  • https://docs.microsoft.com/en-us/aspnet/core/security/enforcing-ssl
  • https://docs.microsoft.com/en-us/xamarin/cross-platform/deploy-test/connect-to-local-web-services#create-a-development-certificate

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

1- Check out this issue https://support.abp.io/QA/Questions/75 2- Also try cleaning your browser cache because some variables are stored in browser's storage.

How to permit Firefox to trust root authorities

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.

  1. Type about:config into the Firefox address bar.
  2. Press the Accept the Risk and Continue button.
  3. Search for security.enterprise_roots.enabled
  4. In the 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.
  5. Restart Firefox to apply changes.

This is a known issue of Firefox. When you go to https://localhost:44389/api/abp/application-configuration You will see Firefox blocks self-signed SSL certificates as seen below:

The solution is simple: Click the Advanced button and then Accept the Risk and Continue.

Hi,

This is a bug and it has been fixed in the next version v2.4.0 on April 3, 2020. The workaround is; replace the marked linke with the below in index.js

window.myBookStore.books.book

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.

Showing 1801 to 1810 of 1850 entries
Made with ❤️ on ABP v9.0.0-preview Updated on September 20, 2024, 05:21