Base solution for your next web application
Starts in:
01 DAYS
01 HRS
01 MIN
01 SEC
Open Closed

Disabling Multi Tenancy causes an invalid Base-64 string error #11012


User avatar
0
ITWebTeam created
  • What is your product version? 11.1
  • What is your product type (Angular or MVC)? MVC
  • What is product framework type (.net framework or .net core)? .net core

Setting MultiTenancyEnabled = false causes "System.FormatException: 'The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters.'" error in startup.cs > app.UseAbpRequestLocalization();

It works find if we leave Multi Tenancy Enabled.

Background: We are upgrading our project's from AspNetZero 8.9.2 to 11.1.

Any help is appreciated.


4 Answer(s)
  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi @rsmith

    Could you share where does this happen ? On the app startup or on a different page ? Could you also try this with a non-modified project ? I couldn't reproduce this on a not modified project.

    Thanks,

  • User Avatar
    0
    ITWebTeam created

    Hi @ismcagdas

    It happens at startup, which prevents the app from starting. We get "HTTP Error 500.30 - ASP.NET Core app failed to start"

    I took a fresh copy that I downloaded of AspNetZero v11.1 of our project and pointed it to the version 8.9.2 database. I ran migrations to update the DB schema. Finally I disabled multi tenancy and ran the application.

    I was able to recreate the issue. So it doesnt like something in the Database, which is odd because we have multi tenancy disabled in the 8.9.2 version.

    Do you have any idea what area of the DB we should start looking for the issue?

    Thank you.

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi @rsmith

    Could you try this in Google Chrome's incognito mode ? Or, you can try clearing your browser cookies and local cache and try after that ?

  • User Avatar
    0
    ITWebTeam created

    Turns out version 8.9.2 didn't encrypt the setting Abp.Zero.Ldap.Password and version 11.1 does. I wasn't getting the cryptography error until I enabled all exceptions. Removing the old value and entering it using the GUI solved the issue.