Thanks @jason.smith, looks promising :)
Hi Jason,
Might also have to do the same - could you shed some light on how you downgraded? I don't see any options to do so using the CLI
Thanks in advance
Hi,
We added the access token as a bearer token as you suggested but still get the same error:
> Request starting HTTP/1.1 POST https://app--dev1.websites.net/api/app/ProfileTest application/json 179
> 2020-11-17 01:06:45.627 +00:00 [INF] Authorization was successful.
> 2020-11-17 01:06:45.629 +00:00 [INF] Executing endpoint '..ProfileTests.ProfileTestAppService.CreateAsync (..Application)'
> 2020-11-17 01:06:45.631 +00:00 [INF] Route matched with {action = "Create", controller = "ProfileTest", area = "", page = ""}. Executing controller action with signature System.Threading.Tasks.Task`1[..ProfileTests.ProfileTestDto] CreateAsync(..ProfileTests.ProfileTestCreateDto) on controller ..ProfileTests.ProfileTestAppService (..Application).
> 2020-11-17 01:06:45.641 +00:00 [ERR] The required antiforgery cookie ".AspNetCore.Antiforgery.w5W7x28NAIs" is not present.
> 2020-11-17 01:06:45.647 +00:00 [INF] Authorization failed for the request at filter 'Volo.Abp.AspNetCore.Mvc.AntiForgery.AbpAutoValidateAntiforgeryTokenAuthorizationFilter'.
> 2020-11-17 01:06:45.648 +00:00 [INF] Executing HttpStatusCodeResult, setting HTTP status code 400
> 2020-11-17 01:06:45.649 +00:00 [INF] Executed action ..ProfileTests.ProfileTestAppService.CreateAsync (..Application) in 17.294ms
> 2020-11-17 01:06:45.650 +00:00 [INF] Executed endpoint '..ProfileTests.ProfileTestAppService.CreateAsync (..Application)'
> 2020-11-17 01:06:45.678 +00:00 [INF] Request finished in 79.3745ms 302
> 2020-11-17 01:06:45.709 +00:00 [INF] Request starting HTTP/1.1 GET https://app--dev1.websites.net/Error?httpStatusCode=400
To clarify - this is a third party app independently developed that simply needs to call the ABP REST API and make a POST. It was working fine prior to updating to 3.3.1. This is now impacting business and we need a resolution. Can we please organise a video call to go over the issue and resolve?
Thanks
Hi,
We have called the IdentityServer connect endpoint and received a token - please provide detail on how this should now be used to make successful POST calls
We are getting the following error when attempting to POST from a mobile application to the ABP REST API
> Request starting HTTP/1.1 POST https://app--dev1.websites.net/api/app/ProfileTest application/json 179
> 2020-11-17 01:06:45.627 +00:00 [INF] Authorization was successful.
> 2020-11-17 01:06:45.629 +00:00 [INF] Executing endpoint '..ProfileTests.ProfileTestAppService.CreateAsync (..Application)'
> 2020-11-17 01:06:45.631 +00:00 [INF] Route matched with {action = "Create", controller = "ProfileTest", area = "", page = ""}. Executing controller action with signature System.Threading.Tasks.Task`1[..ProfileTests.ProfileTestDto] CreateAsync(..ProfileTests.ProfileTestCreateDto) on controller ..ProfileTests.ProfileTestAppService (..Application).
> 2020-11-17 01:06:45.641 +00:00 [ERR] The required antiforgery cookie ".AspNetCore.Antiforgery.w5W7x28NAIs" is not present.
> 2020-11-17 01:06:45.647 +00:00 [INF] Authorization failed for the request at filter 'Volo.Abp.AspNetCore.Mvc.AntiForgery.AbpAutoValidateAntiforgeryTokenAuthorizationFilter'.
> 2020-11-17 01:06:45.648 +00:00 [INF] Executing HttpStatusCodeResult, setting HTTP status code 400
> 2020-11-17 01:06:45.649 +00:00 [INF] Executed action ..ProfileTests.ProfileTestAppService.CreateAsync (..Application) in 17.294ms
> 2020-11-17 01:06:45.650 +00:00 [INF] Executed endpoint '..ProfileTests.ProfileTestAppService.CreateAsync (..Application)'
> 2020-11-17 01:06:45.678 +00:00 [INF] Request finished in 79.3745ms 302
> 2020-11-17 01:06:45.709 +00:00 [INF] Request starting HTTP/1.1 GET https://app--dev1.websites.net/Error?httpStatusCode=400
Hi,
Also getting this issue after upgrading to 3.3.1 - seems to only be affecting POST calls via the API/Swagger
Can you please post some detailed code on this IdentityServer token endpoint we should be calling instead of the account login?
Sure thing, is there anything we can do with DbContexts to make this as close to ABP as possible?
Hi,
In that case can you please advise what would be the best practice approach within ABP to achieve this?
For example, should we discard the concept of navigation properties and just rely on id mapping?
Thanks
Hi,
Thank you for that - I note in the example that you are using the string after the '@' in the email address to identify tenancy.
What we are trying to do is get the user email address and check it against the database for a matching record and thus a matching tenant. Is this possible?
A user won't have a tenant email address as they will be using their personal email. In this case your example does not help.
Thanks
Hi,
Could you please point us in the direction of some example code on how to achieve this?
Thanks