Can you give me minimal steps to produce the issue ?
what was the your abp version. What is your current ABP version ? 7.4 ? (I just want to sure) Can you share your package.json? did you remove the lock file after the update ?
Error messages created with ConfirmService. if you want to override. you should replace the service with Angular Dependency Injection system.
https://docs.abp.io/en/abp/7.3/UI/Angular/Confirmation-Service
the code: https://github.com/abpframework/abp/blob/dev/npm/ng-packs/packages/theme-shared/src/lib/services/confirmation.service.ts
Or if you want to change how to handle error , you can https://github.com/abpframework/abp/blob/dev/npm/ng-packs/packages/theme-shared/src/lib/services/router-error-handler.service.ts
I fix the issue. The problem was npm install throw error. but yarn works. If user execute yarn in .suite/schematics folder. The issue will fixed. The problem was peer dependencies. It have fixed. Maybe you can update your project latest version of 7.3.x. it will be fixed.
okay but can u share the step please
remove yarn.lock,
package-log , node_modules and .angular and re instal with yarn.can you explain more in steps how can i do that
the error is "@volo/ngx-lepton-x.core" is not found. maybe you should check app.module.ts. Can you share your app.module.ts ?
the simplest way remove the permission that name is AbpIdentity.SettingManagement
then user cannot seen the settings.
But if you want to remove the compenent in settings. Create a provider. Then add app.module.ts as provider. Then get settingsTab service and remove it. (I highly suggested permission based solution)
import { SettingTabsService } from '@abp/ng.setting-management/config';
import { APP_INITIALIZER } from '@angular/core';
import { eIdentitySettingTabNames } from '@volo/abp.ng.identity/config';
export const IDENTITY_SETTING_TAB_PROVIDERS = [
{
provide: APP_INITIALIZER,
useFactory: configureSettingTabs,
deps: [SettingTabsService],
multi: true,
},
];
export function configureSettingTabs(settingtabs: SettingTabsService) {
return () => {
settingtabs.remove([eIdentitySettingTabNames.IdentityManagement]);
};
}
Hi LinchArnold! Thank you very much for supporting me. It is work.
Hello mahmut! Solution of LinchArnold is working. we can refer to create a new document.
I happy to hear that. We are still working on the issue. Domain based issuer validation issue should be fixed. There is an internal issue too.
you can modify the field with "Dynamic form extensions" feature. you mah read the documentation. https://docs.abp.io/en/abp/latest/UI/Angular/Dynamic-Form-Extensions here the value is.
{
type: ePropType.String,
name: 'valueType',
displayName: 'AbpIdentity::ValueType',
sortable: true,
columnWidth: 200,
valueResolver: data => of(data.getInjected(ClaimsComponent).getTypeName(data.record.valueType)),
},
contributor field name is eIdentityComponents.Claims
yes I have tested with Seperated auth server options and there is an issue. I couldn't login with tenant. I have opened an issue and I am working with teammate that expert in backend.
By the way sorry i have made mistaked. The app template name is not called as "tiered". That option is called --separate-auth-server
. We are working on the issue.
Hello, I have compared between my configuration and your configuration in your git hub link . My configuration is same to your configuration. When my project deployed to Azure Kubernetes Service, the isssue still existed. I cannot login in my tenant angular. As you can se in the below image API token can be called successfully and return access_token, but angular cannot redirect to home page
I think we can disscuss in a online meeting like goole meeting or zoom meeting, because you can seee my project more detailed If you cannot arrange the time for a online meeting, I will send you my source code, you can take a look and help me to fix the wrong configuration. So that I can deploy to Azure Kubrentes Service and report you the reulst.
To better assist you, we're arranging a special 1:1 online meeting – a deviation from our usual support process. This dedicated session will allow us to address your concerns effectively. Kindly share your preferred time, and we'll ensure a seamless meeting experience. Feel free to contact me at mahmut.gundogdu@volosoft.com to coordinate the meeting details.
Yes
Could you describe the steps for producing the issue ?
Because if you add ThemeShared module, abp-modal should work as expected. because it defined in there. You can check the coude. https://github.com/abpframework/abp/blob/dev/npm/ng-packs/packages/theme-shared/src/lib/theme-shared.module.ts
We need to produce the issue for finding solution.