Activities of "464199480"

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.

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

Hi

Which version to use?

I used when 9.0.0 to create an empty template, but no Account External Provider

The template has confirmed that SSO is enabled

  context.Services.AddAuthentication()
      .AddGoogle(GoogleDefaults.AuthenticationScheme, options =>
      {
          options.ClaimActions.MapJsonKey(AbpClaimTypes.Picture, "picture");
      })
      .WithDynamicOptions<GoogleOptions, GoogleHandler>(
          GoogleDefaults.AuthenticationScheme,
          options =>
          {
              options.WithProperty(x => x.ClientId);
              options.WithProperty(x => x.ClientSecret, isSecret: true);
          }
      )
      .AddMicrosoftAccount(MicrosoftAccountDefaults.AuthenticationScheme, options =>
      {
          //Personal Microsoft accounts as an example.
          options.AuthorizationEndpoint = "https://login.microsoftonline.com/consumers/oauth2/v2.0/authorize";
          options.TokenEndpoint = "https://login.microsoftonline.com/consumers/oauth2/v2.0/token";

          options.ClaimActions.MapCustomJson("picture", _ => "https://graph.microsoft.com/v1.0/me/photo/$value");
          options.SaveTokens = true;
      })
      .WithDynamicOptions<MicrosoftAccountOptions, MicrosoftAccountHandler>(
          MicrosoftAccountDefaults.AuthenticationScheme,
          options =>
          {
              ////options.WithProperty(x => x.ClientId);
              options.WithProperty(x => x.ClientSecret, isSecret: true);
          }
      )
      .AddTwitter(TwitterDefaults.AuthenticationScheme, options =>
      {
          options.ClaimActions.MapJsonKey(AbpClaimTypes.Picture, "profile_image_url_https");
          options.RetrieveUserDetails = true;
      })
      .WithDynamicOptions<TwitterOptions, TwitterHandler>(
          TwitterDefaults.AuthenticationScheme,
          options =>
          {
              options.WithProperty(x => x.ConsumerKey);
              options.WithProperty(x => x.ConsumerSecret, isSecret: true);
          }
      );

Does it mean that we need to add @ctrl/tinycolor to package.json in future versions

Has the issue been fixed?

hi Please advise the last version number that is no longer maintained If the latest is not available, I will give up updating the module