expires_in value for OAuth2.0

[riza-khan]

Hello,

Curious if this is configurable with Kulala. I'm authenticating with Oauth 2.0, which works great, but the expires_in value is 10 milliseconds. So after the first request, I have to authenticate again. The token should be valid for 1hr.

I'm not experienced to know if this is a Kulala config, or an issue with the auth provider. Could you enlighten me?

Thank you,

[YaroSpace]

The expiration time is usually set by the auth provider.
The expire_in = 10 (seconds) is set internally in Kulala for Grant types that do not provide expiration time (this is an implementation detail to allow to resume your request after authentication).
But, I am now thinking that I should add a check, so it does not get overridden if it did get provided.

What grant type are you using?

[riza-khan]

"Grant Type": "Authorization Code",

Is it also a bug that after every request I have to reauthenticate?

[YaroSpace]

most likely. Give me a few mins, I will push a potential fix.

[YaroSpace]

Pushed an update to develop. See if it helps.

[riza-khan]

Ok, now the expires_in value is no longer overridden when I reauthenticate! That seems to have solved a bunch of the frustrating issues I was facing (having to constantly authenticate).

Thank you so much for the speedy fix!

[YaroSpace]

It is a pleasure. Thanks for bringing it up!