Authentication problems

[tomstarley]

Sometimes I’m having trouble loading it. I can go to get.kasban.io, and click Get Access Now. That takes me to the screen where I normally authenticate. Often though, the Kasban logo at the top of the page does not load, and I’m unable to click the authenticate button. Refreshing the page a couple of times seems to fix this, but I’m not sure if this is a browser issue or trouble with the authentication flow. I’ve attached a screenshot – I don’t know if you’ve seen something similar before. I’ve also asked our platform team to take a look to make sure the authentication process here is secure. - Ceri

[tomstarley]

[alexdunne]

The authentication error seems to be very sporadic. It seems to only affect certain users and these users are not affected 100% of the time. From what I can tell, it is something to do with the refreshing of the auth_token as it only happens to users that have already authed and are trying to reauth when their token expires. There are also no errors in the console*.

Observing the problem it seems as though the user correctly reaches the Asana OAuth page and returns back to Kasban. However, when the user returns they are still not correctly authed until after a few refreshes when it then fixes itself.

I have attempted to replicate the problem on my own machine and on the live site by changing the auth_token and token_death such as:

• Changing the token_death to an expired time
• Changing the auth token characters slightly
• Deleting one of the two keys
• Denying myself access on the oauth asana page and then re-allowing access
• Incognito mode
• Different browsers
• A mixture of the above...

Yet I still cannot replicate this myself.

I have added a bunch of console logging in #242 to hopefully spot the error.

*There could be a 412 error which is expected https://asana.com/developers/api-reference/events

[tomstarley]

Heres a video of the issue: https://youtu.be/_S2trI-Vgzk

[tomstarley]

[tomstarley]

The problem seems to be at https://github.com/SmoofCreative/kasban/blob/develop/app/actions/index.js#L817. The request is fired and it seems to get a token, however, it does not run the then or catch portion of the promise. The network tab reports a cancelled when trying to access kasban.io which could be causing the problem, however, this is within the asana library. A google search shows that this could be an issue surrounding the window.location on Chrome.

[markchua]

Hi guys (from Asana). Do you have the steps to consistently repro this issue? I'm having trouble following exactly what is happening. I'll try my best to help debug the issue, but I'm just as perplexed as you are.

Can you try adding a try/catch handler around the whole thing- I think the error might be occurring outside the promises which is why it isn't getting into the then/catch. Hopefully we can get a bit more visibility into what is happening. Thanks!

[alexdunne]

Hey @markchua, sorry to say I have found no way to replicate this on my own machine. From what I've seen this doesn't effect all users but the users it does effect are able to replicate it consistently by changing the token_death time thus forcing the token refresh.

Typically, the effected users (that I know of for certain) are the product owner and the two Asana guys we have skyped with!

I've just pushed up the try catch you suggested so hopefully that sheds some light on the situation. Thanks for your help!

[markchua]

Btw if anybody can see the new errors please do update here as I will be taking a look when theres an actionable update.

[tomstarley]

Hey guys! I've got the bug back on my chrome - here's the latest screenshot of the console. We've just heard back from asana. They want to send a newsletter and feature on the app page. Can't tell you how badly i want to get to the bottom of this bug. Open to ideas as to how we can make that happen. @markchua if you want to take control of my machine to review feel free.

[tomstarley]

@alexdunne if its only effecting the owner of asana is it worth you creating a new account and work space to see if you can replicate the issue? I may try the same here.

[markchua]

@tomstarley So it looks like you can replicate this pretty consistently. How can we set this up so we can debug together? Also what do you mean by the "owner of asana"?