Activities of "liangshiwei"

maybe related to the identity session.

could you try logout first, then re-login.

then navigate to Account/sessions

you should be able to see two sessions.

i will check it

Hi，

They already have built-in support

Do we need a 2. DbContext for all TenantDBs (with MultiTenancySide=Tenant)?

no, you don't.

Does the DbMigrator support migrations and data seeding without extra modification for a multi-tenant architecure with separate tenant dbs? (assuming everything else is correctly set up)

yes, without any change.

How do we customize the seeding data for every tenant (like, a admin user with a certain password)?

See https://abp.io/docs/latest/framework/infrastructure/data-seeding

If running the DbMigrator separately (with dotnet run), how does the DbMigrator find out which tenants are new and need to be setup and data seeded?

it will seed all tenant's data, so you have to make sure idempotence

your original question is about Issuer validation failed. Issuer: 'https://localhost:44322/'. Did not match: validationParameters.ValidIssuer: 'null' or validationParameters.ValidIssuers: 'https://{0}.localhost:44322/'.

HI,

I mean the webapp, httpapi and authserver logs.

I am deploying to Azure, so I can turn on logging there?

will it work locally?

I have 'Require Two-Step Verification for my users' unchecked - they enter there user id and password and then again they are redirected and again asked for user id and password .

could you share the full logs

Hi,

i think this is a new question, could you please create a new ticket, thanks.

already refunded.

Please, show me how to create and configure multiple environment appsettings files (appsettings.Development.json, appsettings.Production.json) in the DbMigrator project so that I don't have to change the values of OpenIddict Applications when migrating to the remote database.

you just need to create an appsettings.Production.json JSON file. And update the DbMigrator.csproj

  <ItemGroup>
    <None Remove="appsettings.Production.json" />
    <Content Include="appsettings.Production.json">
      <CopyToPublishDirectory>PreserveNewest</CopyToPublishDirectory>
      <CopyToOutputDirectory>Always</CopyToOutputDirectory>
    </Content>
  </ItemGroup>

then you are use then dotnet run --environment Production command

By the way, I don't see the changes (remove and modify some properties of an entity) applied to the existing documents in MongoDb after running the DbMigrator. Does the DbMigrator (for MongoDb) apply the changes to the existing documents or only apply to the new ones? Or do I have to manually update the changes to the existing documents?

how do i reproduce this

please create a new ticket, thanks