Add scope on refreshAccessToken()

[ashish-budhraja]

Without adding scope refreshAccessToken is considering default scope resulting in invalid_scope response from the API

[Skullbock]

Thanks!

[tm1000]

This broke our workflow because we use offline tokens and we set the scopes in the first online creation of the offline token. The result of changing this as a semver bugfix release meant that when we went to get offline access tokens the scopes were empty (because we do not pass scopes we only define scopes on the initial get of the token) thus suddenly all API calls started failing as it trickled up through our infrastructure because scopes went from. null to []. So Zoho no longer used the default

If Zoho did oauth like any sane individual following the oauth spec this wouldnt be an issue

I'd say in the future be more cautious of changes like this

[tm1000]

This is actually a result of: thephpleague/oauth2-client#1030 (comment)

But its all related

[tm1000]

Once thephpleague/oauth2-client#1053 is merged this PR itself should be reverted

[Skullbock]

Yeah agree. On both the revert and with zoho being… peculiar with oauth 🤣 Daniele Rosario CTO Weble.it <http://weble.it/> Via Giuseppe Zampieri 3 36100 Vicenza +39 0444 130094 <+390444130094> +39 328 3017134 <+393283017134> Il giorno lun 23 dic 2024 alle 22:59 Andrew Nagy ***@***.***> ha scritto:

…

Once thephpleague/oauth2-client#1053 <thephpleague/oauth2-client#1053> is merged this PR itself should be reverted — Reply to this email directly, view it on GitHub <#34 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAINRUY6ALQNRLWYB3XM3EL2HCBSLAVCNFSM6AAAAABT3AW3XWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRQGM2TONRWHE> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>