Yes, the backend is configured as described and the external logins page was there until we upgraded the application to v8.3.4 and the front-end (angular) to v9.0.4 based on the recommendation in this ticket. Now the external logins configuration page has disappeared.
@liangshiwei - Thank you for providing this. This gives us what we need. If I may make a couple of suggestions.
This is not an answer to my question. You cannot generate a new solution from newer versions of ABP Suite. How do I install a specific version of ABP Studio?
For business reasons (not technical), we cannot upgrade to .NET 9. We must continue building and developing our solutions on .NET 8. Therefore, we need to continue using the 8.3.4 version for some time.
As of now, we cannot use ABP Studio. I can install the 0.9.8 version of the CLI from the command line and use that to generate new solution templates. However, if I launch ABP Studio, it updates the version of the CLI. Your design choices for version management assume everyone is able and willing to upgrade to .NET 9. We cannot do that which makes the tool useless to us.
I have the same problem. In addition, trying to login to ABP Studio gives the following message.
Thank you!
We are using Angular and have not edited the UI. I sent you an invite to the GitHub repo.
<PackageReference Include="Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX" Version="3.2.1" />
Ignoring it may be an option, but it spams the log file with these messages every 5-10 seconds. This issue showed up after upgrading from 8.1.4 to 8.2.1. In the meantime, since it does not appear to be affecting the user experience, I will configure the logs to filter these messages.
The Abstractions package was already implicitly referenced in several of the projects. I explicitly added it to the *Domain.Shared project but that had no affect. I am still getting the warnings. I also tried putting the explicit reference in the HttpApi.Host project and tried explicitly referencing Volo.Abp.AspNetCore in the HttpApi.Host project. In all cases, I still get the warning/error shown below.
[13:16:56 WRN] Could not load type 'Volo.Abp.AspNetCore.WebClientInfo.IWebClientInfoProvider' from assembly 'Volo.Abp.AspNetCore, Version=8.2.1.0, Culture=neutral, PublicKeyToken=null'. System.TypeLoadException: Could not load type 'Volo.Abp.AspNetCore.WebClientInfo.IWebClientInfoProvider' from assembly 'Volo.Abp.AspNetCore, Version=8.2.1.0, Culture=neutral, PublicKeyToken=null'. at Volo.Abp.AspNetCore.SignalR.Auditing.AspNetCoreSignalRAuditLogContributor.PreContribute(AuditLogContributionContext context) at Volo.Abp.Auditing.AuditingHelper.ExecutePreContributors(AuditLogInfo auditLogInfo) [13:16:56 WRN] Could not load type 'Volo.Abp.AspNetCore.WebClientInfo.IWebClientInfoProvider' from assembly 'Volo.Abp.AspNetCore, Version=8.2.1.0, Culture=neutral, PublicKeyToken=null'. System.TypeLoadException: Could not load type 'Volo.Abp.AspNetCore.WebClientInfo.IWebClientInfoProvider' from assembly 'Volo.Abp.AspNetCore, Version=8.2.1.0, Culture=neutral, PublicKeyToken=null'. at Volo.Abp.AspNetCore.SignalR.Auditing.AspNetCoreSignalRAuditLogContributor.PreContribute(AuditLogContributionContext context) at Volo.Abp.Auditing.AuditingHelper.ExecutePreContributors(AuditLogInfo auditLogInfo)
It was already using the AbpUnitTestSqliteConnection but it was not disabling the UnitOfWorkTransaction. I added the following line to the CmsKitProEntityFrameworkCoreTestModule ConfigureServices method.
context.Services.AddAlwaysDisableUnitOfWorkTransaction();
I haven't seen it fail since in the new project.
This does not help. We know how to serve the Angular application as part of the API. The complication comes when trying to get OpenIddict components working with this configuration. I am guessing there are other people who also want to deploy applications both the Angular SPA and the .NET API under a single domain. A recipe book or guide for this would be very helpful.
