That makes sense. Do you have a link to the issue, so I can get notified when its ready? Google login is required for us, as we use it to authenticate employees of our company. This way we don't have to manage accounts in multiple systems. Acually, it would be best if google is the only login option, so without the username/password. Can this be configured for the mvc module?
Hi, we also have a license from before 16 jan (2021-11-25), would be great if it is included. But we're willing to pay for a pdf version. Where can we get that? Amazon only sells the e-book version, if I understand correctly?
Thanks, that link works for me. Got the pdf version.
An endpoint always throws an Exception (as test). I expect this endpoint to return a 500 with json, and on a local develop environment it does. However on production the endpoint returns a 400 with html.
What causes this?
hi, thanks for the quick reply.
That makes sense, I found the code and removed app.UseDeveloperExceptionPage();
However, I still get the a 500 with json. This is what I except, as an exception is thrown. However, what I don't understand is why on production a 400 with html is returned. This should also be a 500 with json, isn't it? I'm not aware of specific code to change this for production.
2022-07-05T09:35:48.145810880Z [09:35:48 ERR] The required antiforgery cookie ".AspNetCore.Antiforgery.nixphHDAMN4" is not present.
After removing the cookies from postman, the request returned as excepted. I'm not sure why these cookies are there, maybe after a unauthorised request?
Thanks, your hint made me digging through the logs, and I see more 400 requests. For example after a DependencyResolutionException which happen during a deployment. So if I understand correctly, exceptions like AntiForgery and DependencyResolutionException are returned with statuscode 400?
This behaviour is unwanted for certain endpoints. For example a webhook, called from Azure event grid, to push messages. When event grid receives a 400, it won't retry the message. At a 500 it does.
Can this be disabled for certain endpoints, or do you have a suggestion how to solve this otherwise?
Hi ABP team,
i have a question about account creation. We would like to create account for new employees and prepare that before they start their onboarding. But this process is a bit cumbersome at the moment.
Two requirements:
What we do now to create an account with google authentication:
We would like to improve this proces. Can you point us in a direction how to do this? Are we encountering a (known) bug or desired (to be build) feature of the framework or should we change our implementation?
Thanks a lot!
Hi Anjali,
thanks for the quick response. Using a default role helps, newly created users will see something. This resolves the 'remove cookies' step.
However, I'm still figuring out how to bypass the enable self registration step. We use the ABP commercial package which seem to handle all user management and registration. I could not find the pages/account folder to put the register.cshtm file in. Is there a way to modify this behaviour?
Another question with regards to the ABP commercial package: does it contain functionality to connect a google login after account creation?
Thank you!
Hi Anjali,
does it contain functionality to connect a google login after account creation? can you explain it with the scenario i am not able understand.
for example when we create user accounts, it would be convenient to have the following steps:
Step 3 is, as far as I know, not possible at the moment? Note: we use the commercial packages.