Starts in:
2 DAYS
4 HRS
15 MIN
5 SEC
Starts in:
2 D
4 H
15 M
5 S

Activities of "ianbaddock"

That IP listed in the screenshot is my local IP. I followed those steps exactly.

I would expect that the solution should work out of the box and that I should have to resort to Android Studio to make it work.

finally figured it out for anyone else experiencing the same issue.

  1. using visual studio, Build > Clean Solution
  2. in the root folder of your source code run: abp clean
  3. using visual studio, Build > Rebuild Solution
  4. after closing the abp suite, reload the abp suite and reopen your solution

I have also just compared my suite templates to that of my team members and mine are not the same. It appears the attempted upgrade to 8.0.1 and then downgrade, didnt reset the code templates. How do I reset these? I have uninstalled and reinstalled abp cli and suite numerous times to resolve with no luck. I would like to just reset the code generation templates to v7.3.2

aaah I assume you have to do it without using the abp suite?

I am not sure how to add the navigation property to the file management entities. I cannot see them in the list.

Perfect, thanks. It is working.

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.

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

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

[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?

Showing 1 to 10 of 16 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06