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.
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?
I think I noticed something: when I included the source code of the module in the Angular project with 'abp add-module Volo.Identity.Pro', the 'log in with this user' button appeared, but when I installed the original '@volo/abp.ng.identity': '~8.3.0', it doesn't show up. I'm not sure if there's an issue with the library.
I tried the Layered Authentication Server in both a separated and a non-separated project, but the same issue occurred. :(
Yes, I know it won't appear for the admin user, but in the scenario you mentioned, it's not appearing either. I forgot to mention that earlier.
The logged-in user is an admin, and the 'Impersonation' permission appears to be active in the role settings.
