#1
|
|||
|
|||
Jdownloader API Token
Hi,
I crafted myself a website somewhere between 1 and 1 1/2 years and plugged it between a RSS reader API and the Jdownloader API. Everything is working perfectly and the code has not changed much on my side. When I log in to the API, it saves all the needed tokens in cookies. When I refresh the page, it makes a "listdevices" call. No issue on this side. Now I started to have some "issues" with the RegainToken a few months back. I log in a T0. From T0 to T+5, if I refresh the page, I'm still logged in the API and the listdevices call is working as expected. From T+5 to somewhere like T+19 or T+20, I have the TOKEN_INVALID and I'm able to reconnected to the API and refresh the tokens via the reconnect call. But after T+20 I get the AUTH_FAILED error and I'm unable to reconnected to the API and have to redo the connection with user+password again. I used to the able to use the reconnect call 24hours after the initial connection but now it looks like the regaintoken is only valid for somewhere arround 20 minutes. Is this a bug in the API or something has changed to make the regaintoken's life so short ? It is a bit annoying to have to do the complete reconnection only 20 minutes after the initial one. Thanks. |
#2
|
||||
|
||||
I've disabled reconnect for unknown appIDs last year. Disabled = set max session timeout to 5 minutes. There has been and still is a client application that logins for EACH api call and that one filled up hundrets of millions of unused sessions waiting for never to happen reconnect. You can send us your appID(of your client) to support@jdownloader.org and I will whitelist it with next server maintenance.
__________________
JD-Dev & Server-Admin |
#3
|
|||
|
|||
Thank you for your answer. I'll check that when possible.
|
#4
|
||||
|
||||
Just contact us via support@jdownloader.org and I will try to help/whitelist your application
__________________
JD-Dev & Server-Admin |
Thread Tools | |
Display Modes | |
|
|