Add a noninteractive authenticator #159
Conversation
Add an authenticator that stores refresh tokens an an application secret, so that it can be serialized/deserialized and used in a non-interactive program.
…ens using another authenticator Expose a way to create `NoninteractiveTokens` using another (presumably `InstalledFlow` or `DeviceFlow`) authenticator. It makes a request for tokens, and then stores just the refresh token, assuming that the access token will be expired by the time it's used. There's no clean exposed way to refresh the refresh tokens, but it's easy to do (if somewhat awkwardly) by creating a new builder using a current NoninteractiveFlow authenticator, so this feature doesn't add it.
|
Hi, may I know if there is any follow up on this feature, or at least a temporary workaround? |
| /// typically short-lived, this authenticator assumes it will be expired and only stores the | ||
| /// refresh token. | ||
| #[derive(Deserialize, Serialize, Clone, Default, Debug)] | ||
| pub struct NoninteractiveTokens { |
There was a problem hiding this comment.
It may be that you have good reasons to implement this, but it looks similar to storage::JSONTokens. Maybe you can reuse that type, as the storage requirements seem to be very similar (store/retrieve by scope).
Good point, I'm sorry for not having come back to this. It looks like a useful addition, and I'd merge it once the conflicts are resolved! |
|
Is there a difference between this |
I think in principle it would have the same effect. I find this flow slightly more transparent and could see some use cases for this, even though the effect would be the same when using an appropriately implemented InstalledFlowDelegate. |
This pair of commits adds another authenticator, which is guaranteed to be non-interactive and just uses stored refresh tokens obtained from a previous authenticator. I want to use this in an offline job that I run periodically, which I build once using a helper binary to generate the
NoninteractiveTokens, and then can use repeatedly. This authenticator is simple and guaranteed to just error out if it can't provide tokens, instead of trying to do something interactive.