we have shared the bare minimal project without depedencies for you to reproduce the issue locally.
I can't use the project you shared before, as I said in the meeting, you should provide a project and steps that only depend on the local PostgreSQL database.
I remember another friend had agreed to do this in the meeting,
Yes, please check your email. We have just shared the project that depends on local PostgreSQL database. Kindly confirm.
hi
The remote check may be affected by the network speed, we can give it a try.
Please send me an email when you're online. liming.ma@volosoft.com
hi, As discussed during meeting, we have shared the bare minimal project without depedencies for you to reproduce the issue locally. Please your email and advise on next steps.
basically you can save all the generated tokens in a database table, when a new request comes, you'll query the database
did you try this https://stackoverflow.com/questions/36151800/asp-net-mvc-identity-securitystamp-signout-everywhereCan you please suggest on point #3. We have a vulnerability open which asks to Encrypt the JWT payload using the JSON web encryption (JWE) scheme. Does ABP supports it, please advise on steps to fix it.
Any update on this request? please advise.
hi @Repunjay
I can confirm that the error is because the database used by DbContext is not generated by its migration.Even if they have the same database table.
I can't run your project correctly, can you check it yourself?
When you share a project that reproduces the problem, you should remove all irrelevant dependencies.
hi maliming, I understand that you can't run the project due to depdencies but I can confirm for sure that the issue we are encountering is not due to database migration. To give you some idea -
Any idea what could cause #5? It's difficult for us to create such a project for you with minimal depdencies and that is why wanted to have a call with you so that you can share any inputs to fix the issue. Kindly help and advise.
Thanks...
hi
Although it took me a long time to run your application, it is not easy to execute. I need to delete a lot of environment information that I don’t have, But I think I found the problem. Your application uses the wrong migration.
The
SCV.Litmus.IdentityServer
has own migrations file. but the migrations inSCV.Litmus.EntityFrameworkCore.DbMigrations
project is the right migration that app will use.Everything is works when I connectiong to the database generated by
SCV.Litmus.EntityFrameworkCore.DbMigrations
in theSCV.Litmus.IdentityServer
.So please try to understand and check your migrations.
hi, The Identity server and core service is working as expected for us and we are using the correct migration. As we mentioned earlier, the problem is with the profile service. If you try to invoke SampleController of profile service, you should be able to reproduce the error we are are encountering.
I believe that I can see the problem remotely, but it is not convenient to solve the problem remotely, and there may be network problems.
Can you make a minimal project that reproduces the problem?
Have shared the minimal project over email which should help you in reproducing the problem. Please confirm if you have received it.
hi
Can you share a project that can be run in my local? The project you shared before can't run.
Hi maliming, It's not feasible for us to share the entire solution code as it contains 60+ projects. We can explain the issue thru screen share over a call.
hi
You can create a new project, and then replace the database provider to npgsql to check whether our built-in features can be works
Can you try? This can rule out the problem with npgsql.
We created a new project and used npgsql database provider and it works fine. But the same thing is not working in our upgraded projects.
Thanks for the update.
Would you also refer us some guideline/help to implement 2FA in Angular UI. We have an urgent requirement to implement 2FA into our application.
hi, Is there any update to this requirement? Please advise to implement 2FA in Angular UI.
hi
Maybe this is a bug of
npgsql
.https://github.com/npgsql/efcore.pg/issues/1859
You can create a new project, and then replace the database provider to npgsql to check whether our built-in features can be works.
We are using Volo.Abp packages in our projects and there is no direct reference to 'npgsql' or any other database provider nuget package in our projects. The database provider package used in our projects is 'Volo.Abp.EntityFrameworkCore.PostgreSql'. Request you to please advise on the fix. Our developer can connect with you over call to discuss on this issue. We never encountered such issue before doing ABP upgrade.
Please note that the github issue you mentioned is also raised by our team member who is working on migrating the projects to ABP 4.3 and .Net 5.