FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login
    1. Home
    2. ethalacker
    3. Topics
    E
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 4
    • Best 1
    • Controversial 0
    • Groups 0

    Topics created by ethalacker

    • E

      Blazor WASM auth

      Q&A
      • • • ethalacker
      29
      0
      Votes
      29
      Posts
      68.4k
      Views

      mark.robustelliM

      @cody Thank you for sharing!

    • E

      MVC Application that routes to different (fusion auth) tenants

      Q&A
      • • • ethalacker
      4
      0
      Votes
      4
      Posts
      1.5k
      Views

      T

      Not sure if this helps, as we don't currently use different tenants at this point in time, but we do for sure enforce sending the tenant id to each call:

      When you setup the OpenIdConnectOptions ---

      private const string TenantIdParameterName = "tenantId"; ... options.Events.OnRedirectToIdentityProvider = context => { /* Fusion auth has the option for multiple tenants - when multiple tenants enabled, we have to ensure we hit the right one for user auth. */ context.ProtocolMessage.SetParameter(TenantIdParameterName, authSettings.TenantId.ToString()); } options.Events.OnRedirectToIdentityProviderForSignOut = context => { context.ProtocolMessage.ClientId = authSettings.ClientId.ToString(); context.ProtocolMessage.SetParameter(TenantIdParameterName, authSettings.TenantId.ToString()); return Task.CompletedTask; };

      Not sure if that helps you - you will have to look at the current HttpContext to decide what you want to do.