Access dropbox file - Authentication failed because the remote party has closed the transport stream

Yes.

do you speak about this ? 

Link 

@Lukag Try read again the thread I linked to. There have been all steps shown. That you have posted is the thing you don't need encoded mandatory - i.e. execute by hand single time only outside your application. The last step, you skipped above, is mandatory to reside in your code. It may generate new access tokens whenever needed. I don't know how to say it more clear!

I thought that the token was quite alway the same.

So.. the first step i must autenticate the app / user by this :

https://www.dropbox.com/oauth2/authorize?client_id=<APP_KEY>&response_type=code 

After i use  https://api.dropboxapi.com/oauth2/token

Example: code flow access token request

Right ? 

I understood the nonsense I was saying, I continue to study. Thank you

Do you understand that there are different tokens? 🧐

---

Lukag wrote:

...

Duration token is 4 hours, if generate now and tomorrow i'll use it in my app , the server'll answer me that token in expired / invalid ...

---

What token do you take in mind above? 🤔

Read again entire thread here and linked resources. 👆 Don't jump over!

i dont understand some steps.

Duration token is 4 hours, if generate now and tomorrow i'll use it in my app , the server'll answer me that token in expired / invalid . So should i refhresh by Api ? 

---

Lukag wrote:

... Can i do it run time by api ?  

---

Definitely NO! API cannot self authenticate. 🙂 If that was possible, it would be a big security HOLE.

Actually, the refresh step in my description above (that you don't like) does exactly this, but it's different thing. There refresh token is used for authentication (valid refresh token). 😉

My scenario in where by web app my customer look and open his file in dropbox. 

Just one form or two, just one user or two. 

I think that token access should be good. However if in future my scenario will change i'll change also my code. 

So , if you agree with me i'll continue on this way .

So i'll need generate a new token every time. Can i do it run time by api ?  

Hm..🤔 To be honest, I don't understand what you mean. Maybe the actual question should be do you need long term access or not?! This is your design decision though. 😉

If you need a single shot (i.e. something that would be run occasionally) application for your own use only, getting access token every time might be better (and simplest) solution. In all other cases use of some form of OAuth might be better solution (my proposal is the simplest OAuth flow for long term use - it is suitable for server side applications, as your looks like according your description).

The decision is yours.