Activities of "464199480"

Hi ! I applied this piece of code, but the issue still remained unsolved.

Could you copy the code of Microsoft.AspNetCore.Authentication.MicrosoftAccount? The ClientSecret obtained in the code is encrypted content.

[Dependency(ReplaceServices = true)] [ExposeServices(typeof(ExternalProviderSettingsHelper))] public class MyExternalProviderSettingsHelper : ExternalProviderSettingsHelper { private readonly ISettingDefinitionManager _settingDefinitionManager; private readonly ISettingEncryptionService _settingEncryptionService; private readonly ICurrentTenant _currentTenant; private readonly AbpExternalProviderOptions _externalProviderOptions; private readonly ISettingManager _settingManager; private readonly IJsonSerializer _jsonSerializer; public MyExternalProviderSettingsHelper( ICurrentTenant currentTenant, IOptions<AbpExternalProviderOptions> externalProvidersOptions, ISettingManager settingManager, IJsonSerializer jsonSerializer, IStringEncryptionService stringEncryptionService, ISettingDefinitionManager settingDefinitionManager, ISettingEncryptionService settingEncryptionService) : base(currentTenant, externalProvidersOptions, settingManager, jsonSerializer, stringEncryptionService) { _settingDefinitionManager = settingDefinitionManager; _settingEncryptionService = settingEncryptionService; _currentTenant = currentTenant; _externalProviderOptions = externalProvidersOptions.Value; _settingManager = settingManager; _jsonSerializer = jsonSerializer; }

Using your approach will result in the clientSecret configured by tenant in the setting being ineffective.

Ok. How to solve the problem of failed login from External provider now? The Client secrets obtained by my provider are encrypted.

Why is it necessary to encrypt the Client secret? This leads to a very serious disaster in the update of the Release environment, and this is not mentioned in the migration instructions.

• ABP Framework version: v9.1.0
• UI Type: Angular
• Database System: EF Core (SQL Server)
• Exception message and full stack trace:
• Steps to reproduce the issue:

All Client secrets are not displayed and this has affected the OAuth login. The Client secret acquisition is encrypted.

Got it

Is binding to existing username not currently supported when logging in via SSO?

Need to log in with a username for SSO binding?

Angular environment that can be reproduced

const oAuthConfig = {
  issuer: 'http://localhost:44372/',
  redirectUri: baseUrl,
  clientId: 'BookStore_App',
  responseType: 'password', // change to password
  scope: 'offline_access BookStore',
  requireHttps: false,
  impersonation: {
    userImpersonation: true,
    tenantImpersonation: true,
  },
};

I confirm that the external provider is enabled

But still not displayed

External providers have come out

I used 9.0.4

But there is still no documentation of external logins

I seem to have spotted the issue

I create this via abp new Acme.Demo-u angular

Angular templates do not appear to have external login associations