RE: Angualr2 Tenant Subdomain #2646

4 Answer(s)

• 

  0

  cangunaydin created 7 years ago

  Hello David, I was having the same issue. To fix the first issue. you need to change code in your AppPreBootstrap.ts in your angular app.

  private static getApplicationConfig(callback: () => void) {
          return abp.ajax({
              url: '/assets/appconfig.json',
              method: 'GET',
              headers: {
                  'Abp.TenantId': abp.multiTenancy.getTenantIdCookie()
              }
          }).done(result => {
  
              let subdomainTenancyNameFinder = new SubdomainTenancyNameFinder();
              var tenancyName = subdomainTenancyNameFinder.getCurrentTenancyNameOrNull(result.appBaseUrl);
  
              AppConsts.appBaseUrlFormat = result.appBaseUrl;
              AppConsts.remoteServiceBaseUrlFormat = result.remoteServiceBaseUrl;
  
              if (tenancyName == null) {
                  AppConsts.appBaseUrl = result.appBaseUrl.replace(AppConsts.tenancyNamePlaceHolderInUrl + ".", "");
                  AppConsts.remoteServiceBaseUrl = result.remoteServiceBaseUrl.replace(AppConsts.tenancyNamePlaceHolderInUrl + ".", "");
              } else {
                  AppConsts.appBaseUrl = result.appBaseUrl.replace(AppConsts.tenancyNamePlaceHolderInUrl, tenancyName);
                  AppConsts.remoteServiceBaseUrl = result.remoteServiceBaseUrl.replace(AppConsts.tenancyNamePlaceHolderInUrl, tenancyName);
              }
  
              callback();
          });
      }
  

  It should be fine when you change this part of AppPreBootstrap.ts

  for the second issue. I didn't know very well about it but if you are using abp v1.4 i suggest you to upgrade it to abp v1.5 cause they have fixed couple of problems in the new release related with tenancy resolver. Good luck with it. Best

  Save Cancel
• 

  0

  paradoxit created 7 years ago

  cangunaydin that worked for the logout null issue thanks! :)

  Save Cancel
• 

  0

  michaelhilgers created 7 years ago

  Hi,

  I'm using Abp 1.5.0 with angular2 and Asp.net core. My appconfig.json looks like: { "remoteServiceBaseUrl": "https://pm-host.mydomain.com", "appBaseUrl": "https://pm-{TENANCY_NAME}.mydomain.com" }

  My appsettings.json looks like :

  "App":{ "WebSiteRootAddress": "https://pm-{TENANCY_NAME}.mydomain.com/", "CorsOrigins": "https://pm-tenant1.mydomain.com,https://pm-tenant2.mydomain.com }

  I changed the AppPreBootstrap function to avoid the <a class="postlink" href="https://pm-null.mydomain.com">https://pm-null.mydomain.com</a> as follow

  let subdomainTenancyNameFinder = new SubdomainTenancyNameFinder();
              console.log('1. appBaseUrl : ' + result.appBaseUrl);
              var tenancyName = subdomainTenancyNameFinder.getCurrentTenancyNameOrNull(result.appBaseUrl);
              console.log('2. tenancyName : ' + tenancyName);
              AppConsts.remoteServiceBaseUrl = result.remoteServiceBaseUrl.replace(AppConsts.tenancyNamePlaceHolderInUrl, tenancyName);
  
              AppConsts.appBaseUrlFormat = result.appBaseUrl;
              AppConsts.remoteServiceBaseUrlFormat = result.remoteServiceBaseUrl;
  
              if (tenancyName == null) {
                  AppConsts.appBaseUrl = result.appBaseUrl.replace('-' + AppConsts.tenancyNamePlaceHolderInUrl, "");
              } else {
                  AppConsts.appBaseUrl = result.appBaseUrl.replace(AppConsts.tenancyNamePlaceHolderInUrl, tenancyName);
              }
  

  To show the tenancy name I wrote the consol.log in the preBootstrap function and I could see that the tenancy name was correct but the application didn't change the tenant.

  I'm always logged in as host tenant.

  Any suggestions ?

  Save Cancel
• 

  0

  ismcagdas created 7 years ago

  Support Team

  Hi,

  Thanks a lot @cangunaydin :). As I remember we also fixed it in AspNet Zero but @ParadoxIT and @MichaelHilgers don't have latest version I think.

  @ParadoxIT, @MichaelHilgers About tenant detection problem, there was a bug in ABP framework and we have fixed it. So if you upgrade your ABP nuget packages, this should be fixed.

  If you don't want to upgrade ABP version, you can implement a custom tenant resolver, see <a class="postlink" href="https://aspnetboilerplate.com/Pages/Documents/Multi-Tenancy#determining-current-tenant">https://aspnetboilerplate.com/Pages/Doc ... ent-tenant</a> to fix this problem.

  Thanks.

  Save Cancel