feat: Remove refresh_token grant type from automated refresh #3706
+29
−156
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SA key flow is designed for machine 2 machine communication, so using
refresh_tokendoesn'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_tokengrant 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'srefresh_tokengrant type isn't OAuth compliant as it doesn't requireclient_id(which is mandatory).I've tested that everything works running the

backgroundrefreshexampleChecklist
make fmtexamples/directory)make test(will be checked by CI)make lint(will be checked by CI)