[17:44:15 WRN] Code:Volo.Authorization:010001 [17:44:15 INF] AuthenticationScheme: Identity.Application was challenged. [17:44:15 INF] Executed action Volo.Abp.Account.ProfileController.GetAsync (Volo.Abp.Account.HttpApi) in 3.0496ms [17:44:15 INF] Executed endpoint 'Volo.Abp.Account.ProfileController.GetAsync (Volo.Abp.Account.HttpApi)' [17:44:15 DBG] Added 0 entity changes to the current audit log [17:44:15 DBG] Added 0 entity changes to the current audit log [17:44:15 INF] Request finished HTTP/1.1 GET https://localhost:44303/api/account/my-profile - - - 401 0 - 10.6009ms
Hi
I am getting the 401 response, but the body is still being returned with the login page:
Is there anything else in the code that needs to be done to remove the body from postman? Do i need to implement the ForwardDefaultSelector code as per your example?
body even for JWT authentication
As per your previous thread, this has a negative effect when using the MVC front end:
Every request comes up like this. I am logged in as the master user account
If you are using the MVC you don't need to set the ForwardDefaultSelector.
How to reproduce the problem using the default template?
I have created a non-tiered MVC solution using EFCore. Added a single entity to my solution. I added the swagger auth as specified in the ABP documentation.
added the default forward as per your suggestion:
and then called it from Postman which now works as expected(no body returned AND 401), but if i login to the MVC UI I receive that error when i try to browse to my entity page. If i remove the ForwardDefaultSelector code it works in MVC
If you're creating a bug/problem report, please include followings:
With the migration from identity server to OpenIdDict, how do we perform the postman authentication flow. If we wish to allow external clients to connect to our API, what is the auth method we use. With identity server, it would be the client_id/client_secret.
what do we use now?
Could you provide some screenshots of a working postman with login returning a bearer token and then using that in postman for a simple get request.
I managed to create an OpenIdDict login which returned a token. I tried to use the token as a bearer token on the next request but it is returning a 401.
Perfect, thanks. It is working.
I have included the file management module in my solution and I would like to create a table for Media which has a navigation property to the files stored in FmFileDescriptors. My solution would allow for upload reports/images/videos which are stored in the files table, but I am creating a gallery on top of the files using the Media table as my gallery source. I would prefer not to use the files tables directly as I need to make many modifications to the schema as well as have other related tables for meta data (EXIF data) and tagging data.
I am not sure how to add the navigation property to the file management entities. I cannot see them in the list.
aaah I assume you have to do it without using the abp suite?
I am generating an entity using the ABP suite and all the code is still coming out with the template tags in it.
Earlier today, I attempted to upgrade my solution from 7.3.2 to 8.0.1. I updated the CLI and the ABP Suite, I then upgraded the ABP packages too. Tried it out and wasnt too comfortable with the outcome. I then discarded all my solution changes, putting the entire solution back to 7.3.2. I uninstalled the ABP cli and Suite and reinstalled the correct version. I then tried to add a new entity and all the generated code sill has all the template tags. How do I resolve this?
