Hi,
OK, thanks for letting me know. I'll mark this as answered.
Thanks again.
Steve.
Hi Steve,
We're aware of that, but it's related to Microsoft UseCors middleware, not ABP Framework. Also, you don't need to add the frontends to any service. Because services should access to gateway not the front end side.
Regards.
So, just to confirm, this is expected?
Are there any work arounds or do we just have to live with it outputting errors into the logs?
Thanks,
Steve.
Hi, i'm seeing CORS errors in the log files for the 5.3.4 microservice template. This is happening for all of the services.
It's not causing any issues and everything works as expected, it's just filling the log file with noise as it happens a lot.
The services (saas, administration, identity, product) only have the Web Gateways in there CorsOrigins configuration. The Web Gateways then have the frontend in their CorsOrigin. So when it goes "frontend -> gateway -> service" i assume Ocelot is passing the Origin as the frontend and that's causing the error?
Is there a way around this? Or do i just need to add the frontends to the services CorsOrigins to stop the errors?
Cheers,
Steve.
Hi,
That works great thanks!
Cheers,
Steve.
Can you try creating a new claims principle using claims from azure ad (employeeId) and add it to current userprinciple when onTokenReceived event?
Hi,
Thanks for getting back to me.
Do you mean the OnTokenResponseReceived event?
In that event I can’t see where I would get the current user principle. I can access the claims principal, but I believe that’s just the user that authenticated with Azure. At the point that OnTokenResponseReceived is fired I’m not sure we have access to any other user principle?
Cheers,
Steve
You can check this class as sample of adding custom claims using custom claims principal factory.
Hi,
Thanks for that. I can now add claims to the abp user.
What would be the best way to take a value from the Azure user claims (such as the employeeid i have) and get it added to the abp user?
In the linked example it looks like the claims value is being taken from a cookie that is being set by some middleware. I'm not sure that'll work in my scenario.
Cheers,
Steve.
Hi,
I'm currently using the microservice template (v5.1.3)
I'm trying to figure out how to make a custom claim visible to when using CurrentUser.FindClaim in one of my custom services.
I'm using Azure Open Id Connect. The claim is in the returned Id token from Azure as seen below
I'm struggling to understand how to get that to appear as a claim on the currently logged in user.
I followed the instructions in this issue https://github.com/abpframework/abp/issues/42 but much like piresashwin in the last comment the CreateAsync method of the custom ClaimsPrincipalFactory never appears to be called.
Cheers,
Steve.
Wow, not sure how i managed to miss that.
Thanks for pointing me in the right direction.
Cheers,
Steve.
Hi,
I have a couple of questions around error handling. I currently have an angular frontend with a REST API backend
I’m attempting to disable the default error handling for my APIs in the angular frontend.
It appears that you can pass “skipHandleError: true” to the RestService to achieve this. However, I’m automatically generating the service proxies using the abp suite with “abp generate-proxy”. Is there any way to tell this auto generation to set skipHandleError to true?
I’m also struggling to create a custom 404 page. Are there any examples of how to do this?
Thanks,
Steve.
I'll take a look at that, thanks,
Steve.
