feature suggestion: auto refreshing access tokens about oauth2

[scrogson]

Hi @tsubery,

I'm hesitant to put this directly into this library. This library is meant to provide low-level OAuth2 building blocks.

Can you give me an example of how you are using this library so I can better understand what it is that you expect to accomplish?

Specifically, how are you storing tokens for later use?

[tsubery]

My use case is a long running background job that access google's api and collects information periodically. That means I need to store a token that eventually expires and need to be refreshed.

When I wrote the issue I forgot about the immutability of data in Elixir. I was thinking it would be clean and easy to make any request fetch for a new access token using the refresh token when necessary. This would work but the original client would not have the new access token and that might lead to many unnecessary round trips. I understand that this library does not implement a token store.

Having said that, there is still some minimal amount of logic can be abstracted away from users like me. All I really want is a token that is good for the next few minutes to do the required work. Maybe a function like this would be useful:

Updated:

def fresh_client_for(client, time_out_seconds) do
  expired_at = client.token.expired_at
   if expired_at && :os.system_time(:milli_seconds) + timeout_seconds < expired_at do
    refresh_token(client, [],[],[])
  else
    client
  end
end

Long running processes could use

fresh_client = fresh_client_for(stored_client, @max_access_time)
OAuth2.Client.get(fresh_client,...

[scrogson]

@tsubery,

Yeah, I've thought about including some sort of token store for a while. However, it seems difficult to make something generic enough to work with all use cases without further thought.

[tsubery]

Yea, seems like it might be mixing too many responsibilities. What do you think about the new function I suggested?

[scrogson]

@tsubery not at this time. Thank you.