Login at oauth procedure not working properly

Question

question

greg asked Aug 7, '19 greg commented Aug 20, '19

Login at oauth procedure not working properly

Since a few days, I noticed an uncommon behavior at my webapp. When I go to login on my page (I implemented the oauth procedure) I get the login window of Clover. After entering e-mail and password, I hit "login", but afterwards I am not logged in, but the login window only changes the word on the button to "Saved". If I hit "Saved" nothing happens, but if I refresh the page I can move on by selecting the merchant and afterwards everything is as usual. In the console of the browser I see a 401 error, following GET is unauthorized: https://sandbox.dev.clover.com/v3/accounts/current?expand=primaryDeveloper%2CprimaryEnterprise%2CprimaryMerchant%2CprimaryMerchant.properties%2CprimaryReseller&_=1525111026127 401 (Unauthorized) (I changed a bit the last number, as I don't know if/what it reveals about my account)

Is it a problem on Clover's side? I am not aware of having changed anything of my code that could have an influence on this.

OAuth

1

10 |2000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

greg commented · Aug 09, 2019 at 03:47 PM

Is anybody else experiencing this problem? This problem is more or less blocking my further web app development, so would be very thankful for any hints. Since it came out of nowhere I suspect something changed on Clover's side. It seems also the sandbox environment is gradually changed, at least I noticed subtle design changes.

0 ·

Welcome to the
Clover Developer Community

Answer 1 · 2019-08-08T09:08:46Z

greg answered Aug 8, '19 greg commented Aug 14, '19

Over night - so without changing anything - the problem got worse. After choosing the merchant in the login procedure, I get an orange Error box and the Clover logo in gray symbolizes loading forever. I have attached the console output of Chrome, hopefully this helps to clarify what is going on here.

PS: I am using a sandbox account.

screenshot-2019-08-08-at-105559.png (200.4 KiB)

2

10 |2000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

greg commented · Aug 12, 2019 at 12:10 PM

I found out the problem has to do with my sandbox account, because another one works just fine. I will contact Clover directly on this.

0 ·

greg greg commented · Aug 14, 2019 at 03:11 PM

As a note for others with the same problem: The situation has improved, so I can login with my account, however only in the way described in the initial post.

0 ·

Answer 2 · 2019-08-16T20:35:21Z

Frank Faustino Deactivated answered Aug 16, '19 greg commented Aug 20, '19

Thank you for bringing this to our attention. There was an issue with OAuth 6 days ago but it has since been resolved. Can you please provide (in a private comment) your app ID so that I can investigate further? It'll also be helpful if you can post a code snippet of how you're handling authentication on your web app.

1

10 |2000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

greg commented · Aug 20, 2019 at 10:56 AM

Hi, thanks for taking care of this issue. However, since Saturday the described strange login behavior has disappeared and everything seems back to normal - I did not change anything!

0 ·

question