Synchronous Communication between Microservices #6506

4 Answer(s)

• 

  0

  Anjali_Musmade created 9 months ago

  Support Team Support Team Member

  Hi,

  please check this similar issue https://support.abp.io/QA/Questions/4558/The-SSL-connection-could-not-be-established-see-inner-exception--BLAZOR-SERVER

  also check this discussion https://github.com/abpframework/abp/issues/11844

  thanks

  Save Cancel
• 

  0

  gterdem created 9 months ago

  Senior .NET Developer

  In the MVC/BlazorServer apps, you can see a configuration as below under the OpenIdConnect configuration:

  if (Convert.ToBoolean(configuration["AuthServer:IsOnK8s"]))
      {
          context.Services.Configure<OpenIdConnectOptions>("oidc", options =>
          {
              options.MetadataAddress = configuration["AuthServer:MetaAddress"]!.EnsureEndsWith('/') +
                                        ".well-known/openid-configuration";
  
              var previousOnRedirectToIdentityProvider = options.Events.OnRedirectToIdentityProvider;
              options.Events.OnRedirectToIdentityProvider = async ctx =>
              {
                  // Intercept the redirection so the browser navigates to the right URL in your host
                  ctx.ProtocolMessage.IssuerAddress = configuration["AuthServer:Authority"]!.EnsureEndsWith('/') + "connect/authorize";
  
                  if (previousOnRedirectToIdentityProvider != null)
                  {
                      await previousOnRedirectToIdentityProvider(ctx);
                  }
              };
              var previousOnRedirectToIdentityProviderForSignOut = options.Events.OnRedirectToIdentityProviderForSignOut;
              options.Events.OnRedirectToIdentityProviderForSignOut = async ctx =>
              {
                  // Intercept the redirection for signout so the browser navigates to the right URL in your host
                  ctx.ProtocolMessage.IssuerAddress = configuration["AuthServer:Authority"]!.EnsureEndsWith('/') + "connect/logout";
  
                  if (previousOnRedirectToIdentityProviderForSignOut != null)
                  {
                      await previousOnRedirectToIdentityProviderForSignOut(ctx);
                  }
              };
          });
  

  You should be setting [AuthServer:IsOnK8s] to true since you are running it on containers; which means you will be logging in through the browser but obtaining/validating the tokens through the internal network. Set the [AuthServerMetaAddress] to real DNS. Set the [AuthServerMetaAddress] to internal docker service address.

  Save Cancel
• 

  0

  abp4@feelaware.com created 9 months ago

  Hi,

  please check this similar issue https://support.abp.io/QA/Questions/4558/The-SSL-connection-could-not-be-established-see-inner-exception--BLAZOR-SERVER

  also check this discussion https://github.com/abpframework/abp/issues/11844

  thanks

  thank you for your help.

  I checked it and The general web - gateway - service route works well, but this phenomenon only occurs in communication between microservices.

  Save Cancel
• 

  0

  gterdem created 9 months ago

  Senior .NET Developer

  Okay, now I understand.

  First, for microservice-to-microservice calls, we introduced Integration Services. We strongly recomment using integration services for this kind of usage.

  If you want to keep using existing authorized endpoints, you probably have IdentityClient configuration as below:

  "IdentityClients": {
      "Default": {
        "GrantType": "client_credentials", 
        "ClientId": "BookStore_OrderService",
        "ClientSecret": "1q2w3e*",
        "Authority": "https://localhost:44322", -> On production this must be the internal service name
        "Scope": "ProductService"
      }
    }
  

  Instead of using https://10.200.40.25:44322 try using docker service name something like http://myauthservice.

  The token validation etc should be (will be) done through the internal network.

  Save Cancel