Refresh token becames Invalid

Hi Vladimir,

This Session duration on Sugar 7 blog post that I wrote a while back should give you a full picture on how it all fits together and most of the client/server side possible causes.

Hope it helps

Hi, Enrico,

Thank you.

I've already checked  refresh_token_timelife (before asking). In this case getting token returns this value, but in my case I've got default period (14 days).

Maybe it can be something else?

Vladimir,

The blog post probably only indirectly covers the subject.

You should check:

• Do PHP sessions last long enough? If not why? Do you use file system or memcached or redis or what? If memcached, see if evictions can terminate earlier the session?
• Do you have any php errors or sugarcrm messages (eg: change of client ip address that terminates the session, or same user logging in from multiple devices)?

If the PHP sessions lasts long enough (for one reason or another) there should be no reason why the token should expire earlier

Vladimir,

The blog post probably only indirectly covers the subject.

You should check:

• Do PHP sessions last long enough? If not why? Do you use file system or memcached or redis or what? If memcached, see if evictions can terminate earlier the session?
• Do you have any php errors or sugarcrm messages (eg: change of client ip address that terminates the session, or same user logging in from multiple devices)?

If the PHP sessions lasts long enough (for one reason or another) there should be no reason why the token should expire earlier

Hi Enrico,

The problem is becoming refresh_token Invalid (not expired)

Thanks for you help.