Activities of "serhatuysal"

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

Seems like we opened a ticket for nothing, huh?

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

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

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?

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.

Help me please

merhaba

openiddict.pfx dosyanızı kullanabilirsiniz.

dotnet dev-certs https -v -ep openiddict.pfx -p 00000000-0000-0000-0000-000000000000

Bkz. https://abp.io/docs/latest/deployment/configuring-openiddict

Yes, I already followed the steps here and made the necessary adjustments, but the result did not change.

dotnet dev-certs https -v -ep openiddict.pfx -p bf6bc8cb-7dd5-43bc-beba-c5bbaf0f78a4

after

When we encountered the same issue with projects hosted on our own servers, setting the 'Load User Profile' option to 'true' in the IIS pool resolved the problem. However, we now need to deploy our application with a hosting provider, and they have informed us that they cannot change this setting