Activities of "serhatuysal"

Help me please

• ABP Framework version: v8.3.1
• UI Type: Angular
• Database System: EF Core (SQL Server, Oracle, MySQL, PostgreSQL, etc..) / SQL Server
• Tiered (for MVC) or Auth Server Separated (for Angular): yes
• Exception message and full stack trace:
• Steps to reproduce the issue:

Hello, in the production environment of my application, for POST, PUT, and DELETE requests, I am receiving the following error:

2024-10-14 19:27:00.747 +03:00 [INF] Authorization failed for the request at filter 'Volo.Abp.AspNetCore.Mvc.AntiForgery.AbpAutoValidateAntiforgeryTokenAuthorizationFilter'. 2024-10-14 19:27:00.747 +03:00 [INF] Executing StatusCodeResult, setting HTTP status code 400

*..Api.Host application runs in the root directory of IIS, Angular application runs under the root directory /panel path of IIS. (add new pool application)

environment.prod.ts

export const environment = {
  production: true,
  application: {
    baseUrl: '/',
    name: 'BasvuruSistemi',
  },
  oAuthConfig,
  apis: {
    default: {
      url: '',
      rootNamespace: 'BasvuruSistemi',
    },
    AbpAccountPublic: {
      url: oAuthConfig.issuer,
      rootNamespace: 'AbpAccountPublic',
    },
  },
} as Environment;

• ABP Framework version: v8.3.1
• UI Type: Angular
• Database System: EF Core (SQL Server, Oracle, MySQL, PostgreSQL, etc..) / MongoDB
• Tiered (for MVC) or Auth Server Separated (for Angular): yes
• Exception message and full stack trace:
• Steps to reproduce the issue:

When I assign permissions to a user individually, they can view these permissions on their page. However, when permissions are assigned through a role, they are unable to see the role-based permissions on their page. A few page permissions have been assigned to the role for testing purposes, and the user is assigned to this role.

Yes, it worked this way. Are there any other similar features we should be aware of? I couldn't find any information about this in the documentation. In previous versions, we didn’t have to configure it like this.

import { Environment } from '@abp/ng.core';

const baseUrl = 'http://localhost:4200';

const oAuthConfig = { issuer: 'https://localhost:44331/', redirectUri: baseUrl, clientId: 'AbpSolution7_App', responseType: 'code', scope: 'offline_access AbpSolution7', requireHttps: true, impersonation: { userImpersonation: true, tenantImpersonation: true, }, };

export const environment = { production: false, application: { baseUrl, name: 'AbpSolution7', }, oAuthConfig, apis: { default: { url: 'https://localhost:44331', rootNamespace: 'AbpSolution7', }, AbpAccountPublic: { url: oAuthConfig.issuer, rootNamespace: 'AbpAccountPublic', }, }, } as Environment; Is it like this?

My issue still persists even after upgrading the ABP version to 8.3.1.

I opened a new support request because my previous one, Log in with this user" button not visible #8023, was closed. My issue still persists even after upgrading the ABP version to 8.3.1.

But the projects created are still 8.3.0 and not using volo/abp.ng.identity Pro.

Seems like we opened a ticket for nothing, huh?

We are already commercial members, so why wasn't the project created with the *.pro versions when we generated it through ABP Studio?