Hi, here are the brief answers to your questions:
Q1: Is it possible to have a centralized identity management with AbpAccountPro module?
Yes, it is absolutely possible to achieve a centralized identity management system using the AbpAccountPro module.
Q2: If it is possible, we assume that the user and role tables will exist only in the central application, and the client applications will not need these tables. Is that correct?
Yes, this is correct. In this setup, the AbpUsers and AbpRoles tables (and other related tables) will primarily reside in the database of your central identity management application. The client applications will not need these tables.
Q3: Integration options with External Authentication Providers (Keycloak/Azure MFA)?
Yes, it is definitely possible to integrate with external authentication providers like Keycloak or Azure MFA. Here are some resources that may help you:
Q4: When the login screen is opened, can we directly redirect to the Keycloak (external provider) login screen? We don’t want users to have to click a "Login with Keycloak" button again when the login page opens.
You can directly redirect users to Keycloak (or any other external provider). You need to create a "realm" in the Keycloak dashboard, get the related URL and update the Authority section in appsetting.json file for example. (should configure oidc scheme like you would do in a normal .net application - there is no difference -).
Regards.
Hi again, I have checked but unfortunately could not reproduce the problem:
Hi, EngincanV All steps are described in https://abp.io/support/questions/9011/No-db-migrations-for-Entities-in-Modules because this different kind of issue I created separate ticket. Yes, I created new Entity [Promotion] in [DemoSolution] and click "Save and generate":
Hi, thanks for sharing the steps. I'll check and let you know asap. Regards.
Hi, EngincanV But I am talking about DB migrations. Suite knows Entity and all relations within one module (and there are no cross-module entities relations). So why it can not generate db migrations? Is it plans for such in future?
We are building solution to separate some business logic in different modules, so a lot of new Entities are planned inside Modules, and to build always manually it would be a lot of operational risks.
Hi @Viktor, I understand your concerns. There was not any open issue about that but I've created just before (with issue number #19581 / in our internal repository). So, we will try to prioritize it and support in the future.
Thanks for your understanding, regards.
Version is 9.0.3.
But I also tried the version 8.0.7Both failed.
Okay, it's weird to hear "Anytime I run migrations even on brand new solutions I am getting the below error. I have figured out if I comment out both the Identity and OpenIdDict configurations in the DBContext then I can get it to run.".
We've thoroughly investigated the reported problem, but were unable to reproduce it. Given the lack of similar reports and our inability to replicate the problem, it appears to be specific to your local environment, rather than an issue with the ABP Framework.
You may check https://abp.io/support/questions/8437/unable-to-create-migration-on-Module#answer-3a16b459-a5a6-468c-499f-505910c6acfc and see if it fixes your problem or not.
Hi, I guess you are trying to create a new migration with the dotnet ef tool right? Can you please check its version?
dotnet ef --version
Hi, the error message System.Net.Sockets.SocketException (10061): No connection could be made because the target machine actively refused it. indicates that the AuthServer application is trying to connect to an SMTP server, but the connection is being refused.
This is likely due to having a wrong SMTP configuration in the application, and since the background jobs run over and over again when there is a problem (retry mechanism), so by any chance, can you check your SMTP configs and ensure they are correct or not?
Hi, first of all, thanks for the quick reply. Great to hear that, the code is working now. For the first question:
You did not answer about migration files? how can we generate migrations for new Entities which are created in Modules? Is it some bug or it should be done always manually? If it is manual process, so what is then reason to pay for Suite... a lot of logic will be in Modules.
ABP Suite creates migrations and applies them to most of the templates. However, for the module templates, since ABP Suite can't know, which module has relation to which main solution, it's hard to get the migration folder and apply it. So, only for the module template, you should create migrations manually, yes.
Hi, can you please confirm that there is a situation as described in this answer or not?
I would like to reproduce the error in a newly generated solution. Unfortunately, I can't find out how to generate a new solution in a specific (old) version using CLI or ABP Studio... how can I do that? Do I need to downgrade the CLI or the Studio first?
EDIT: Ok, I've figured it out... Uninstall the CLI and reinstall the corresponding version. It would be nice if you could also select the version when creating a solution via ABP Studio.
Hi, we have an internal issue supporting selecting a version when creating a solution, but unfortunately could not prioritize it yet. I'll talk with the team.
Regards.
