Closed gterdem closed 1 year ago
Using the latest version of Ocelot the issue seems to stem from the old config value being "ReRoutes" when it should be "Routes", demo application worked as expected when I did the change
@gterdem I faced the same error when trying to run the project as mentioned in the Microservice Demo Solution.
I rerun the Projects, but this time by authenticating the AuthServer.Host by giving the username and Password and proceed with running other projects in same order.
Now the Issue is not reproduced. By design the Backend Admin App requires this authentication.
I think this is an authentication issue and not related to bug.
Also the document Microservice Demo Solution#Run-Projects should be updated with one additional step of Authenticating the AuthServer.Host before proceeding to running other projects as well.
Can anyone tell me how this permission system work? there is only one PermissionGrant table and I can't see any document about it ... for example how in this table you can prohabit a permission for a user ? or does permission with permission providerKey of "C" can be applied to roles ?
i create multiple microservices but none of them can authorized permission ... the permission are not in claims .. should i make http request to auth-server to check those !?
can you explain how this permission grant table works ?
I read this article several times , but i couldn't understand from which store is going to authorize the permission ? https://docs.abp.io/en/abp/latest/Authorization
for god sake , if my authorization server is separated from micro-service server , from where it the microservice is going to ask for authorizing the permission !?
https://github.com/abpframework/eShopOnAbp is the main sample for microservice now. Closing the issue.
BackendAdminAppGateway: