Starts in:
2 DAYS
7 HRS
19 MIN
18 SEC
Starts in:
2 D
7 H
19 M
18 S
Open Closed

Identity server not working after hosted on AWS #542


User avatar
0
vishalnikam created

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.

  • ABP Framework version: v3.0.4
  • UI type: Angular
  • Tiered (MVC) or Identity Server Seperated (Angular): yes
  • Exception message and stack trace:
  • Steps to reproduce the issue: Identity server not working after hosted on AWS

5 Answer(s)
  • User Avatar
    0
    gterdem created
    Senior .NET Developer

    @vishalnikam,

    Hello, can you share related logs about identityserver? What is the exact problem do you come across?

  • User Avatar
    0
    vishalnikam created

    After enabling https for identity server still discovery shows http. we are using cloudfront --> nlb --> ECS

    Also, try given solution on this but didnt worked

    var forwardOptions = new ForwardedHeadersOptions { ForwardedHeaders = ForwardedHeaders.XForwardedFor | ForwardedHeaders.XForwardedProto, RequireHeaderSymmetry = false };

    forwardOptions.KnownNetworks.Clear(); forwardOptions.KnownProxies.Clear();

    // ref: https://github.com/aspnet/Docs/issues/2384 app.UseForwardedHeaders(forwardOptions);

    https://github.com/IdentityServer/IdentityServer4/issues/1331

  • User Avatar
    0
    alper created
    Support Team Director

    try this

    app.Use((httpContext, next) =>
    {
        httpContext.Request.Scheme = "https";
        return next();
    });
    

    https://github.com/abpframework/abp/blob/dev/docs/en/Migration-Guides/Abp-4_0.md#other-identityserver-changes

  • User Avatar
    0
    vishalnikam created

    It worked but facing differet issue now. We have multiple identity-service instances are running in 2 servers and we are load balancing it behind NLB. The issue is the 1st request goes to Identity server1 and if the second goes server2, it fails saying 401-unauthorized because the server 1 could not able to share the token with server2. we are not using Radis cache and Key. What I have to do to make load balancing working here ? Is anything can be done for shared resources between two Identity server instance?

  • User Avatar
    0
    alper created
    Support Team Director

    you can use AddDataProtection check out https://stackoverflow.com/a/51366568/1767482

Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06