Activities of "sumeyye.kurtulus"

I'm thinking you are saying like this below

async hasLoggedIn(): Promise<boolean> { const authStatus = await this.oktaAuth.isAuthenticated(); return authStatus || this.oAuthService.hasValidAccessToken(); }

this.authService.hasLoggedIn().then(isLoggedIn => {

});

Yes, this is what I mean.

For the granted policies response that you shared, the okta library should not cause a problem. However, I did not see <MyProjectName>.Dashboard.Host and <MyProjectName>.Dashboard.Tenant permissions that is checked by the guard. Is this right?

I am assuming that oAuthService is from angular-oauth2-oidc library. So, you should be able to use this as you have mentioned at the beginning

    this.oktaAuth.isAuthenticated().then(async (authStatus) => {
        if (authStatus) {
            // Authenticated successfully
        }
    });

Hello, yes you are right. You will need to handle this part according to the library you use.

The permission guard only checks the required permissions that you give for the route. However, dashboard component checks for MyProjectName.Dashboard.Host and MyProjectName.Dashboard.Tenant permissions exceptionally.

Here is the reference for the check: https://github.com/abpframework/abp/blob/2201ee1c349da9dff2a0a333434e660f436b0851/npm/ng-packs/packages/core/src/lib/guards/permission.guard.ts#L47

So now the question is: why is the event handler you suggested - this.window.addEventListener('storage', (event) => { ... }) is not fired for the passive tab. As we found out, Permission Guards does not affect this. Do you have any idea what else I could check?

If the XSRF token is managed by the framework, it should update automatically using the approach I mentioned earlier. This should detect login/logout actions and redirect the passive tab to the home page when you log in from the active tab.

If the passive tab is not redirecting and requires a re-login, there might be another issue. I have not been able to reproduce this, so could you check if there is any custom logic preventing the expected behavior?

As you have mentioned, tab-2 uses an invalid XSRF token value. It either uses the old value expecting the new one, or uses the new one and complains about anyway. Could you try storing the value with an alternative way and notify me again?

I am sorry for the delay in getting back to you.

I assume you are using abp-modal for selecting items. Based on your logic, you can open another modal on top of the existing one to add new items that are not in the list.

Here is an example that may guide you through the process:

<!-- Your current modal -->
<abp-modal [(visible)]="isRoleListModalOpen">
  <ng-template #abpHeader>
    <h3>{{ 'Role List' }}</h3>
  </ng-template>

  <ng-template #abpBody>
    <ul>
      <li *ngFor="let role of roles">{{ role }}</li>
    </ul>
    <button (click)="openAddRoleModal()" class="btn btn-primary">
      {{ 'Add New Role' }}
    </button>
  </ng-template>

  <ng-template #abpFooter>
    <button type="button" class="btn btn-secondary" (click)="isRoleListModalOpen = false">
      {{ 'Close' }}
    </button>
  </ng-template>
</abp-modal>

<!-- The modal that will open when you click on add button -->
<abp-modal [(visible)]="isAddRoleModalOpen">
  <ng-template #abpHeader>
    <h3>{{ 'Add New Role' }}</h3>
  </ng-template>

  <ng-template #abpBody>
    <input [(ngModel)]="newRole" placeholder="Enter role name" class="form-control" />
  </ng-template>

  <ng-template #abpFooter>
    <button (click)="saveRole()" class="btn btn-primary" [disabled]="!newRole">
      {{ 'Save' }}
    </button>
    <button type="button" class="btn btn-secondary" (click)="isAddRoleModalOpen = false">
      {{ 'Cancel' }}
    </button>
  </ng-template>
</abp-modal>

You can also get a reference from this documentation: https://abp.io/docs/latest/framework/ui/angular/modal

Let me know if you need further clarification.

Thank you for sharing more details. However, I did not see anything that would cause this cyclical re-login problem in these files. That is why, I suspected whether you have implemented another guard on the home route.

We do not typically close tickets unless they are fully resolved or inactive for some time. We understand the issue you are facing and are actively working on a fix to prevent this from happening again. Thanks for your patience.

Hello, I didn’t fully understand your question. Could you share the steps to reproduce the issue?

Also, if you can include the property types you used when creating the entity and any related navigation details, it will help us find the right solution.

I understand your concern, and I appreciate your detailed observations. To clarify how proxy generation should work in a multi-microservice Angular project, let me walk you through an example setup:

1. I created a project named as MicroserviceTest

2. Then I added these services as my colleague has explained here.

3. Then I created the libraries for the angular project using the angular cli since each library acts as an independent module representing a specific microservice.

   • yarn ng generate library my-service-1
   • yarn ng generate library my-service-2

   The folder structure will look like this

4. Then you can run these commands to generate the proxies for the services you created:

   • abp generate-proxy -t ng -u <ServiceUrl> -m myservice1 --target my-service-1
   • abp generate-proxy -t ng -u <ServiceUrl> -m myservice1 --target my-service-2

Thanks for bringing up the documentation update. Even if updating such comprehensive documentation takes time, we will make sure this point is clearly explained to improve the developer experience. Let me know if you need further clarification!