Hi Guys we already implement the chat modulo with are conditions:
ABP Framework version: v7.2.2
UI type: Angular
DB provider: EF Core
Tiered (MVC) or Auth Server Separated (Angular): yes
For we is very important can grow up the functionalities. we have the questions:
Is it possible that the chat module works with azure signarlr, if so can you give me an example?
I want to modify the chat module message notification message, they tell me to adjust the component (ChatIconComponent)chat-icon.component.ts but I have not been able to do it. could you give me an example?
Hi,
I'd like to know if there is a guide to replace the Ocelot gateway to the Azure API Management.
I am having an issue regarding the routing for the APIs. When we log in, and the system tries to get the required permissions, roles, etc. It throws an error because the routing tries to get the data only fromthe apis like: "api/identity/..." after default endpoint (authserver.com/...), but for Azure API Management we need to configure a suffix for all the APIs, ex. For IdentityService the right URL is "https://apim_route/identityservice/api/identity/..." and the suffix configured is "identityservice", but when we do a request it does the following: "https://apim_route/api/identity/...".
We tried to modify the API routes following the same pattern for new services and checking the JSON for APIs configuration mentioned here in the environment file in this way :
import { Environment } from '@abp/ng.core';
const baseUrl = 'https://flyguys-spa-dev-cus.azurewebsites.net';
const oAuthConfig = {
issuer: 'https://flyguys-authserver-dev-cus.azurewebsites.net/',
clientId: 'Angular',
scope:
'offline_access openid profile email phone AccountService IdentityService AdministrationService SaasService ProductService CoreService FileManagementService',
requireHttps: true
};
export const environment = {
production: false,
application: {
baseUrl,
name: 'Flyguys',
},
oAuthConfig,
apis: {
default: {
url: 'https://flyguys-apim-dev-eus.azure-api.net',
rootNamespace: 'NVC.Flyguys',
},
AbpAccountPublic: {
url: oAuthConfig.issuer,
rootNamespace: 'AbpAccountPublic',
},
ProductService: {
url: 'https://flyguys-apim-dev-eus.azure-api.net/productservice',
rootNamespace: 'NVC.Flyguys.ProductService'
},
AbpIdentity: {
url: 'https://flyguys-apim-dev-eus.azure-api.net/identityservice',
rootNamespace: 'AbpIdentity'
},
AbpAuditLogging: {
url: 'https://flyguys-apim-dev-eus.azure-api.net/administrationservice',
rootNamespace: 'AbpAuditLogging'
},
TextTemplateManagement: {
url: "https://flyguys-apim-dev-eus.azure-api.net/administrationservice",
rootNamespace: 'TextTemplateManagement'
},
LanguageManagement: {
url: 'https://flyguys-apim-dev-eus.azure-api.net/administrationservice',
rootNamespace: 'LanguageManagement'
},
AbpPermissionManagement: {
url: 'https://flyguys-apim-dev-eus.azure-api.net/administrationservice',
rootNamespace: 'AbpPermissionManagement'
},
SettingManagement: {
url: 'https://flyguys-apim-dev-eus.azure-api.net/administrationservice',
rootNamespace: 'SettingManagement'
},
AbpAccountAdmin: {
url: 'https://flyguys-apim-dev-eus.azure-api.net/identityservice',
rootNamespace: 'AbpAccountAdmin'
},
AbpPaymentCommon: {
url: 'https://flyguys-apim-dev-eus.azure-api.net/saasservice',
rootNamespace: 'AbpPaymentCommon'
},
SaasHost: {
url: 'https://flyguys-apim-dev-eus.azure-api.net/saasservice',
rootNamespace: 'SaasHost'
},
AbpFeatureManagement: {
url: 'https://flyguys-apim-dev-eus.azure-api.net/saasservice',
rootNamespace: 'AbpFeatureManagement'
},
CoreService: {
url: 'https://flyguys-apim-dev-eus.azure-api.net/coreservice',
rootNamespace: 'NVC.Flyguys.CoreService'
},
FileManagement: {
url: 'https://flyguys-apim-dev-eus.azure-api.net/mediastorageservice',
rootNamespace: 'NVC.Flyguys.FileManagementService'
}
},
} as Environment;
Could you help us with this approach, please?