Timeline for Access token keeps being invalidated
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S May 23, 2017 at 21:01 | history | edited | Brock Adams | CC BY-SA 3.0 |
added 1 character in body
|
| May 23, 2017 at 11:25 | review | Suggested edits | |||
| S May 23, 2017 at 21:01 | |||||
| Apr 13, 2017 at 12:25 | history | edited | CommunityBot |
replaced http://stackapps.com/ with https://stackapps.com/
|
|
| Jan 3, 2017 at 17:38 | vote | accept | ᔕᖺᘎᕊ | ||
| Jan 2, 2017 at 19:30 | comment | added | ᔕᖺᘎᕊ | Hmmm that's weird then :/ I guess it's worth just keeping it in the back of your mind in case it pops up again... | |
| Jan 2, 2017 at 18:52 | history | edited | ᔕᖺᘎᕊ |
not a bug anymore, figured it out
|
|
| Jan 2, 2017 at 18:52 | comment | added | ᔕᖺᘎᕊ | @BrockAdams sorry, this was entirely my fault. The problem was that I was getting the default expiry of 24 hours which meant users needed to get a new access token every day. Getting a no_expiry token seems to have fixed it. No bug here. Could it be you had the same problem when you faced this issue in the past? :/ | |
| Jan 2, 2017 at 18:50 | answer | added | ᔕᖺᘎᕊ | timeline score: 3 | |
| Jan 1, 2017 at 18:55 | history | edited | ᔕᖺᘎᕊ |
edited tags
|
|
| Jan 1, 2017 at 18:46 | comment | added | ᔕᖺᘎᕊ | @BrockAdams I'll post there tomorrow, I think I should give it at least a day! :P now that's weird, the stats link shows me that the 'app removed user' is always 0, which suggests it's never auto-invalidated, which seems wrong :/ | |
| Jan 1, 2017 at 18:31 | comment | added | Brock Adams | It galls me that API posts are there, but I wouldn't blame you one bit for posting both places. As you said, API stuff gets much more love on MetaSE. Also, your stats are at stackapps.com/apps/oauth . Then click your app listing. Then click the "Authentication Statistics" link in the righthand column. | |
| Jan 1, 2017 at 18:26 | comment | added | ᔕᖺᘎᕊ | @BrockAdams lol I genuinely was thinking of adding one but it's impossible :P looks like it is a bug then, but there isn't any real way for us to debug this is there? can we access data on our application's token's? as in, can we see a history of users requesting tokens or something? that would help I think | |
| Jan 1, 2017 at 18:24 | comment | added | Brock Adams | I upvoted because I think I sometimes see a similar problem (and this may all be related to how SEDE loses your login "every other visit"). But this technically should be closed for lack of an MCVE. ;) | |
| Jan 1, 2017 at 18:22 | history | edited | Brock Adams |
edited tags
|
|
| Jan 1, 2017 at 17:15 | history | asked | ᔕᖺᘎᕊ | CC BY-SA 3.0 |