You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now saving the value of an API token to the session in PHP doesn't actually persist that token between page loads. We need to research a solution to this problem.
A call to the login API is made on every send message action executed in WebTexting. Ideally we would hang on to a single token until it expires and then use the refresh token to get a new token.
This issue is a follow up to the work done in #30.
The text was updated successfully, but these errors were encountered:
uncheckederror
changed the title
Persist data between page loads to efficiently reuse API tokens
[FEATURE] Persist data between page loads to efficiently reuse API tokens
Sep 4, 2024
IIRC the reason we get a new auth token every time we send a message is because the field we are using for auth is stored somewhere in fpbx's default settings. This fpbx default setting ([webtexting][accelerate_networks_inbound_token]) is getting populated from fpbx's db upon fpbx login which prevents persistence of new tokens.
Right now saving the value of an API token to the session in PHP doesn't actually persist that token between page loads. We need to research a solution to this problem.
A call to the login API is made on every send message action executed in WebTexting. Ideally we would hang on to a single token until it expires and then use the refresh token to get a new token.
This issue is a follow up to the work done in #30.
The text was updated successfully, but these errors were encountered: