Kore Authorization Profiles - OAuth v2 Client Credential Token Management

[ahmad.zidan]

Hi,

We’re setting up a service node using Kore’s authorization profiles with OAuth v2 client credentials. We’d like to understand how Kore handles access token management in this scenario. Specifically, does Kore generate a new access token for each request made by the service node, or can the authorization profile reuse existing tokens until they expire?

Thanks

[john.nicholson]

My experience has been that the authorization profile will use the access token until it expires. The profile settings include a place to define the refresh token URL. The service node seems ‘simple’ since the authorization profile is handled through a link under “auth”, but it always works in my bot.