Activities of "ianbaddock"

That didnt work unfortunately.

Can you share the details?

It has the same outcome as the 200 response with the login page HTML when calling from postman.

I added this in postman as per the suggestion but it did not change the outcome:

"Try to add X-Requested-With: XMLHttpRequest header to your request."

hi ianbaddock

If you are using the MVC you don't need to set the ForwardDefaultSelector.

Try to add X-Requested-With: XMLHttpRequest header to your request.

That didnt work unfortunately.

Any other ideas?

Thank you for your detailed explanation. I understood the problem and I talked to the team about the problem, I learned that there is a breaking change for v5.0.0.

You can see the details of the issue here: https://github.com/abpframework/abp/issues/9926

Then I added the marked code in the picture below to test the situation, and it worked fine when I made a request via swagger.

However breaks MVC pages and abp's js proxy scripts, which use ajax.

---

We discuss inside to find the most optimal solution to this problem.

Good morning, yeah I tried that too initially which broke my MVC pages :(

Looking forward to seeing a working solution

I guess you want to send requests via Postman, not via Swagger. That's why you need to get the token first and then make a request with that token.

Hi

I think you missed my point. The API is secured and it should return a 401 if we try to access and endpoint without the token, it should not return a 200 with the login page html (from swagger OR from postman)

this is an older version of ABP which does return the 401 as expected.

Yes, Because this is not a database created by AbpDbContext.

You can give it a try. Just use a normal ef core dbcontext.

perfect, thanks mate

hi You can try to generate a DbContext and use it. https://docs.microsoft.com/en-us/ef/core/cli/dotnet#dotnet-ef-dbcontext-scaffold https://www.learnentityframeworkcore.com/walkthroughs/existing-database

Just to clarify, this would NOT be an AbpDbContext?