Skip to content

Conversation

@JorTurFer
Copy link

@JorTurFer JorTurFer commented Nov 3, 2025

SA key flow is designed for machine 2 machine communication, so using refresh_token doesn't make sense from operational pov as the sessions doesn't need to be extended (like it happens for users that you want to silent refresh).

Using refresh_token grant type it's not needed because for a workload, using the jwt-bearer grant type or refresh token grant type is exactly the same, but SA's refresh_token grant type isn't OAuth compliant as it doesn't require client_id (which is mandatory).

I've tested that everything works running the backgroundrefresh example
image

Checklist

  • No generated code was adjusted manually (check comments in file header)
  • Changelogs
    • Changelog in the root directory was adjusted (see here)
    • Changelog(s) of the service(s) were adjusted (see e.g. here)
  • VERSION file(s) of the service(s) were adjusted
  • Code format was applied: make fmt
  • Examples were added / adjusted (see examples/ directory)
  • Unit tests got implemented or updated
  • Unit tests are passing: make test (will be checked by CI)
  • No linter issues: make lint (will be checked by CI)

Signed-off-by: Jorge Turrado <[email protected]>
@JorTurFer JorTurFer marked this pull request as ready for review November 6, 2025 15:26
@JorTurFer JorTurFer requested a review from a team as a code owner November 6, 2025 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant