Change Tenant UI - Angular - Doesn't work #12131

4 Answer(s)

• 

  0

  oguzhanagir created one month ago

  Support Team

  Hi

  This issue is caused by the browser. There are a few things we can do to fix it in the app.

  Using HTML Meta Tags: On the Angular side, you can add the relevant meta tag to the head section of the layout.

  < head>
      < meta http-equiv="Content-Security-Policy" content="script-src 'self' 'unsafe-inline';">
  < /head>
  

  Adding a middleware like the one below to the Startup.cs file on the server side

  app.Use(async (context, next) =>
  {
      context.Response.Headers.Add("Content-Security-Policy", "script-src 'self' 'unsafe-inline';");
      await next();
  });
  

  I think one of these changes will solve this problem.

  The instructions here will be helpful, you can look at the details here if you want.

  Save Cancel
• 

  0

  dominici created one month ago

  Hi oguzhanagir, I tried both solutions but still not work.

  The server side middleware has no effect.

  The HTML Meta tag on the angular side incresed the number of errors

  My considerations are:

  • I have tried with Chrome, Firefox and Edge. Same behaviour on all browser
  • I made no change on the downloaded angular code and the server side works great. I don't think it's related to code or to browsers, many users would have reported it

  Could be something related to my VS Code? yarn version -> v1.22.10 node version -> v20.15.1 npm version -> v10.7.0

  Is the api IsTenantAvailable response valid and complete?

  Thanks for support.

  Br, Fabrizio

  Save Cancel
• 

  0

  dominici created one month ago

  After a deep investigation , I found the reason.

  I have added on backend side this sserialization formatting rule

              // Improve -> set by default enum to string conversion in serialization
              services.AddControllers().AddJsonOptions(x =>
              {
                  // serialize enums as strings in api responses (e.g. Role)
                  x.JsonSerializerOptions.Converters.Add(new JsonStringEnumConverter());
  
                  // ignore omitted parameters on models to enable optional params (e.g. User update)
                  //x.JsonSerializerOptions.DefaultIgnoreCondition = JsonIgnoreCondition.WhenWritingNull;
              });
  

  So all the enum previously returned as numbers have become strings.

  So, in the "change tenant" function code -> tenant-change-modal.component.ts

              .subscribe((result: IsTenantAvailableOutput) => {
                  switch (result.state) {
                      case TenantAvailabilityState.Available:
                          abp.multiTenancy.setTenantIdCookie(result.tenantId);
                          this.close();
                          location.reload();
                          return;
                      case TenantAvailabilityState.InActive:
                          this.message.warn(this.l('TenantIsNotActive', this.tenancyName));
                          this.focusTenancyNameInput();
                          break;
                      case TenantAvailabilityState.NotFound: //NotFound
                          this.message.warn(this.l('ThereIsNoTenantDefinedWithName{0}', this.tenancyName));
                          this.focusTenancyNameInput();
                          break;
                  }
  

  This switch doesn't match any value and the button simply do nothing :-(

  I'm sorry, it's my fault but I was unlucky to don't get an error.

  Consider adding a default condition in this switch case in order to manage all unexpected values.

  Have a nice day

  Br, Fabrizio

  Save Cancel
• 

  0

  oguzhanagir created one month ago

  Support Team

  Hi

  We're glad you found the solution. Thanks for your feedback, keep up the good work

  Save Cancel