External Providers DynamicOptions not working with "Authority" Property #9174

8 Answer(s)

• 

  0

  maliming created 7 months ago

  Support Team Fullstack Developer

  hi

  You have to assign it a valid value initially, and it will change at runtime based on your current tenant.

  

  Save Cancel
• 

  0

  JimmyLiew created 7 months ago

  Hi, I have assigned a valid Authority value initially. After that, I login to tenant and purposely modify the Authority endpoint to become invalid login1.microsoftonline.com, but the change doesn't seem to take effect. Could you advice?

  Remarks: I have performed clear cache as well.

  

  Thanks.

  Save Cancel
• 

  0

  maliming created 7 months ago

  Support Team Fullstack Developer

  hi

  Can you share a test project that inlcude your ms external login info?

  liming.ma@volosoft.com

  Thanks.

  Save Cancel
• 

  0

  JimmyLiew created 7 months ago

  Hi,

  Sent via email.

  Thanks

  Save Cancel
• 

  0

  maliming created 7 months ago

  Support Team Fullstack Developer

  Thanks. I will check it.

  Save Cancel

  1
• 

  0

  maliming created 7 months ago

  Support Team Fullstack Developer

  hi

  Add to your AuthServer project.

  using Microsoft.AspNetCore.Authentication.OpenIdConnect;
  using Microsoft.IdentityModel.Protocols;
  using Microsoft.IdentityModel.Protocols.OpenIdConnect;
  using Volo.Abp.Account.Public.Web.ExternalProviders;
  using Volo.Abp.DependencyInjection;
  
  namespace AbpMicroservices.AuthServer;
  
  public class MyOpenIdConnectOptionsPostConfigureAccountExternalProviderOptions : IPostConfigureAccountExternalProviderOptions<OpenIdConnectOptions>, ITransientDependency
  {
      public Task PostConfigureAsync(string name, OpenIdConnectOptions options)
      {
          if (!string.IsNullOrEmpty(options.Authority))
          {
              options.MetadataAddress = options.Authority;
              if (!options.MetadataAddress.EndsWith('/'))
              {
                  options.MetadataAddress += "/";
              }
  
              options.MetadataAddress += ".well-known/openid-configuration";
          }
  
          options.ConfigurationManager = new ConfigurationManager<OpenIdConnectConfiguration>(options.MetadataAddress, new OpenIdConnectConfigurationRetriever(),
              new HttpDocumentRetriever(options.Backchannel) { RequireHttps = options.RequireHttpsMetadata })
          {
              RefreshInterval = options.RefreshInterval,
              AutomaticRefreshInterval = options.AutomaticRefreshInterval,
          };
  
          return Task.CompletedTask;
      }
  }
  
  

  Save Cancel
• 

  0

  JimmyLiew created 7 months ago

  Hi,

  Is it necessary to initialize a valid Authority value at first place? Can we leave Authority empty and have it resolved at runtime, similar to how ClientId and ClientSecret are handled? I have tried to leave Authority empty, but it seem not working.

  Thanks.

  Save Cancel
• 

  0

  maliming created 7 months ago

  Support Team Fullstack Developer

  The OpenIdConnect will validate the OpenIdConnectOptions. So you have to set a value initially.

  Save Cancel

  1