hi
We haven't implemented the latest PayU yet.
hi
https://github.com/Flo3Digital/Flo3BlazorDev/commit/65293d6c5f723f365858a037999d3448f13980af
hi
Change Merchant and Signature
"Payment": {
"Payu": {
"Merchant": "TEST",
"Signature": "SECRET_KEY",
btw, We implemented the LiveUpdate(LU) version API of payU.
https://secure.payu.ro/docs/old/lu/
Can you test it in web project, then I will update the web.public.
hi
I have pushed the new commit.
https://github.com/Flo3Digital/Flo3BlazorDev/commit/b349ece4729bbafa4b928a9c1e2d337d5ea94069
hi
This is also the case in the dev environment.
Can I reproduce this with your Flo3BlazorDev project?
If so, what are steps.
Thanks
I have updated the new code to help you to check your configuration.
https://github.com/Flo3Digital/Flo3BlazorDev/commit/bc99a06899f4e60a1c7598ace3fd1cd27cf50e93
[09:37:43 ERR] AuthServer:Authority: https://localhost:44362
[09:37:43 ERR] JwtBearerOptions Authority: https://localhost:44362
[09:37:43 ERR] JwtBearerOptions Issuer: https://localhost:44362/
[09:37:43 ERR] JwtBearerOptions JwksUri: https://localhost:44362/.well-known/jwks
[09:37:43 ERR] JwtBearerOptions ValidIssuers: https://localhost:44362/
hi
I still don't see anything in the deployed API logs
This should be because you did not correctly deploy the latest code to the server.
Your AuthServer:Authority in the staging environment is https://fbd-auth.azurewebsites.net
I think this is the reason.
hi
I don't see any of the JWTBearerOptions logging in the staging logs,
That's strange, We have to check the logs of staging apps.
We need to make sure the configuration is correct.
I have pushed the new commit. Can you try to deploy it again?
Thanks.
hi
Please test the new commits in your stage environment.
https://github.com/Flo3Digital/Flo3BlazorDev/commits/master/
Thanks.
