Hi @musa.demir we added our stripe account timezone to Asia-Kolkata and also tried by setting our enviormnent in central-US with stripe timezone as Central Us but it still gives 302 for that webhook also - https://stripewebapp.azurewebsites.net/Stripe/WebHooks
I have shared the details
Hello we are trying to integrate stripe but the web hook ** https://[www.yoursite.com]/Stripe/WebHooks** giving 302 error for our website which is hosted on azure but it seems to working fine when we are testing it locally using stripe CLI
let us know if any solution is avialable
Thank you Ismail
We tried this option as well by passing expiration time to CreateAccessToken . As you see in above scrrenshot, access token time expire in seconds = 365 days but in actual, it is valid only for 1 day.
Hi,
We are developing a client application where we are exposing APIs to external application. That external application needs a static token instead of calling Authentication API every time when token expires I tried to create seperate API like TokenAuth/Authentication to generate static token valid for 365 days but it seems to be valid only for 24 hours instead of 365 days. I set expiration time for this access token to 365 days but it dosen't seems to be working as expected.
Can you please suggest how we can achieve this through framework?
Thank you Ismail. We will do the changes and keep you posted on this.
We are facing a weird issue in Authenticate API since last couple of days. In our one of client project, our application APIs are used by client's external application to store data. They are using TokenAuthController Authenticate method to generate access token to access these APIs. But, sometimes when they try to generate a token uisng this API, application throws 504-gateway timeout error from this API on Azure environment. In local environment, we are not facing this issue . Could you please proveide some pointers here? Current application uses abp-zero-template- 10.1.0
We are having Client application build on Asp net zero version [ 10.1.0] We upgraded .Net framewotk to 6.0 in the same template version as a part of performance improvement activity. After this we observed that "Login as user" [ Impersonation] is failing in deployed azure application On local machine, there are no issues. Impersonation is working fine but it is not working on deployed Azure application
We referred similar posts on this forums and tried to increase impersonation token timeout from 1 min to 10 min but, no luck.
On deployed site, we are getting following console error =>
polyfills-es2015.263093a5df10c0060b4e.js:1 POST https://devmovescoutproapi.sirva.com//api/TokenAuth/ImpersonatedAuthenticate?impersonationToken=d1849e2c-65d7-4889-beee- scripts.a680bd9980236ce7cd67.js:1 Could not find localization source: AbpWeb
We tried to check logs from server log file but there are no logs found for ImpersonatedAuthenticate method
Can you please provide us the pointers to resolve this issue?
Hello @ismcagdas,
Sorry i did not update you earlier that the above error occurs when we integrate Elsa.net into the aspnetzero public project. We added Elsa packages into the .csproj of the Public project. Then we are geting this error. And it is due to version conflicts for .NET Core 6.0 as you can see from the above screenshot.
We are able to run the version 11.1.0 public project without any error.
Can you please let us know how we can resolve the conflicts. We are using Elsa .Net workflow 2.6.0 which is the latest.
Thanks
Any update on this please ?
