Hi,
After we downloaded a clean version, it is working. A mistake happened when merging lastest versions.
Thank you.
product version: 10.5 product type: Angular product framework: .net core
(OnLazyLoad) eventEmitter not fired when the primeNG (p-table) is in a modal. The problem is general to all the modals. This did not happen before upgrading to the latest version.
Example: When we try to login as a user, the list is always empty because the event is never triggered.
The call to the API is therefore never made.
(code from src\app\shared\common\lookup\common-lookup-modal.component.html)
getRecordsIfNeeds in never triggered
Thank you for your support.
Hi,
Ok perfect, not my prefered approach :D But no worries.
What would be your reccomendation to filter out that user from the normal user administration screen? I would not want the operators to delete or alter that special user. Or maybe show that user only with a special filter? Also avoiding modifications to core ASP.NET Zero pages to avoid updating issues.
Thanks for the help !
Hi @ismcagdas,
Ah I think I understand, basically we might not be using the proper way to connect. Let me talk about the requirement a bit and maybe you can provide a better solution.
Our customer has an external system, and for reporting purposes, that system would need to connect to our API (asp.net zero) and use the business layer here to perform some queries. We're trying to figure out the best way to give access to the API to that system.
Can you reccomend an approach?
Thanks !
@ivanosw1, what solution did you end up chosing for this ? We'll looking at the same context as you.
Thanks !
Hi @ismcagdas,
So if I want another system (does not have the context of a human user) to connect to my API I absolutely need a user ? I'm not sure I see the use of the identity server then ? I could simply setup as user / password directly ?
What am I missing here ?
Thanks !
Angular & ASP.Net Core Asp.Net Zero version 9.3.0 ABP framework 5.14.0
In our project we are trying to allow machine to machine communication. For that, we enabled identity server. We created a client that support client_credentials. We were able to generate an access token with the client id and client secret. When we try to use this token to execute a http request, we always received 403 forbidden.
Is it something missing ?
The steps we took :
Hi @alfreds and @ismcagdas,
We'll be looking into this shortly, Umbraco Headless will of course be on the shortlist. I was wondering though if anyone has experience with other CMS.
Also, is this something that is on the roadmap for Asp.Net Zero, providing basic CMS functionnalities? The types of project we build on AspNet Zero often don't need very elaborate CMS, basic RTE and fields and images often suffice.
I'll chime back in if we move forward on this.
Hi,
This is the link of the issue created :
https://github.com/aspnetboilerplate/aspnetboilerplate/issues/5996