yes but product-service ng-package.json has to be updated with correct schema. need to remove dest key from it which did not handled by update command.. Can you help with a scenario where i want my end users using angular app to be able to login to multiple tenants with single user. we have created a subdomain for each tenant. now using the subdomain url each clinic is identified as tenant by its subdomain. each sub domain will have its on branding images and style. in this case if i want the end user to be able to login across different tenant based on some tenant user association as for current abp framework support only one tenant per user, how can i achieve this. please suggest.
2024-08-12T10:32:57.0381520Z #35 [build 20/20] RUN yarn build:prod --configuration='qa' 2024-08-12T10:32:57.3482641Z #35 0.462 yarn run v1.22.22 2024-08-12T10:32:57.5501568Z #35 0.513 $ ng build product --configuration production && ng build health --configuration production '--configuration='''qa'' 2024-08-12T10:32:57.8692366Z #35 0.983 Workspace extension with invalid name (defaultProject) found. 2024-08-12T10:32:59.1772048Z #35 2.291 Building Angular Package 2024-08-12T10:32:59.3439169Z #35 2.457 An error has occurred while validating config at /app/projects/product-service/config 2024-08-12T10:32:59.4534466Z #35 2.476 Configuration doesn't match the required schema. 2024-08-12T10:32:59.4534952Z #35 2.476 Data path "" must NOT have additional properties (dest). 2024-08-12T10:32:59.4535183Z #35 2.507 error Command failed with exit code 1. 2024-08-12T10:32:59.4535661Z #35 2.508 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. 2024-08-12T10:32:59.4536235Z #35 ERROR: process "/bin/sh -c yarn build:prod --configuration=${configuration}" did not complete successfully: exit code: 1 2024-08-12T10:32:59.4661970Z ------ 2024-08-12T10:32:59.4662840Z > [build 20/20] RUN yarn build:prod --configuration='qa': 2024-08-12T10:32:59.4663182Z 0.462 yarn run v1.22.22 2024-08-12T10:32:59.4663650Z 0.513 $ ng build product --configuration production && ng build health --configuration production '--configuration='''qa'' 2024-08-12T10:32:59.4664070Z 0.983 Workspace extension with invalid name (defaultProject) found. 2024-08-12T10:32:59.4664390Z 2.291 Building Angular Package 2024-08-12T10:32:59.4665150Z 2.457 An error has occurred while validating config at /app/projects/product-service/config 2024-08-12T10:32:59.4665616Z 2.476 Configuration doesn't match the required schema. 2024-08-12T10:32:59.4665952Z 2.476 Data path "" must NOT have additional properties (dest). 2024-08-12T10:32:59.4666269Z 2.507 error Command failed with exit code 1. 2024-08-12T10:32:59.4666554Z 2.508 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. 2024-08-12T10:32:59.4666981Z ------
i was able to figure out. but only one issue noticed that whatever port i expose, yarp only somehow works with port 8080 even if specify port 80 or 44367 it works only when i mentione port 8080 in yarp for some reason. any idea?
Hi im trying to configure yarp to configure intercomuunication of microservices hosted in single vm.
yarp example :
below is network bridge name
"Administration": {
"Destinations": {
"Administration": {
"Address": "http://network-bridge:44367/",
}
}
}
or below docker ip:
"Administration": {
"Destinations": {
"Administration": {
"Address": "http://172.17.0.1:44367/",
}
}
}
or
below with container name :
"Administration": {
"Destinations": {
"Administration": {
"Address": "http://administrationsvc:44367/",
}
}
}
ocelot.json used to work fine with containeranme as host path. nothing seems to be working. please suggest.
what is the use of abplinkusers table in identity service?
we have intial solution of abp .version 7.3 and we were able to migrate to version 8.0 successfully with the help of abp support. Now we are trying to migrate abp version from 8.0 to 8.2.1. after migrating and running the auth server getting below error in administration service.
Microsoft.IdentityModel.Tokens.SecurityTokenMalformedException: IDX14100: JWT is not well formed, there are no dots (.). The token needs to be in JWS or JWE Compact Serialization Format. (JWS): 'EncodedHeader.EndcodedPayload.EncodedSignature'. (JWE): 'EncodedProtectedHeader.EncodedEncryptedKey.EncodedInitializationVector.EncodedCiphertext.EncodedAuthenticationTag'. ---> System.MissingMethodException: Method not found: 'Byte[] Microsoft.IdentityModel.Tokens.Base64UrlEncoder.UnsafeDecode(System.ReadOnlyMemory`1
please fins the logs file attached here : https://drive.google.com/file/d/1VuuObaM-9P0vcAUnUYpMqxwpDIoPDNlG/view?usp=sharing
please find the logs at : https://drive.google.com/drive/folders/148gFlQJA1JnkC3k4Dd0aHV5WQLTIsF-o?usp=sharing
we observer that we are getting 404 error on the url https://localhost:44325/api/permission-management/permissions?providerName=U&providerKey=3a119289-b1c3-4980-f238-793a348dd78d while for roles same url : https://localhost:44325/api/permission-management/permissions?providerName=R&providerKey=admin is working.
From Users menu if click on permission url: https://localhost:44325/api/permission-management/permissions?providerName=U&providerKey=3a119289-b1c3-4980-f238-793a348dd78d Giving 404 error
internal calling identity service url : https://localhost:44388/integration-api/identity/users/3a104ca8-2d0b-0494-3653-5e7e48633bd5/role-names?api-version=1.0 which is failing. Also noticed that the url in the browser is just /roles and not /role-names.
From Roles menu click permission: https://localhost:44325/api/permission-management/permissions?providerName=R&providerKey=admin working fine.
still the migration process is a single step no multiple. so you should answer all related questions in one single thread.
event after uninstalling payments module we are seeing the same error. moreover , we observer that the same url with different params working.
From Users menu: https://localhost:44325/api/permission-management/permissions?providerName=U&providerKey=3a119289-b1c3-4980-f238-793a348dd78d Giving 404 error users menu internal calling identity service url : https://localhost:44388/integration-api/identity/users/3a104ca8-2d0b-0494-3653-5e7e48633bd5/role-names?api-version=1.0 which is failing. Also noticed that the url in the browser is just /roles and not /role-names.
From Roles: https://localhost:44325/api/permission-management/permissions?providerName=R&providerKey=admin working fine.
