Google Oauth 2.0 2-Legged OAuth WorkAround

[dmel...@topcloud.io]

Hello support team,

Regarding Google OAuth 2.0 integration, I recently noticed that, in case where a unique account is used for integration, we can bypass consent screen and refresh_token storage...

Instead, it's possible to create a Service Account which will manage Server to Server Applications (https://developers.google.com/identity/protocols/OAuth2ServiceAccount) (2-Legged-OAuth).

It looks less complicated than OAuth 2.0/3-Legged-OAuth (as we all usually do) but I am blocked at JWT Creation (https://developers.google.com/identity/protocols/OAuth2ServiceAccount#creatingjwt).

Is anybody already tried it? If yes, please get back to me with a workaround. It will make me save a lot of time for future integrations.

Thank you in advance.

Best regards.

[Murali]

Hi Dimitri,

We are working on your query will update you on the SFDC case #2046 raised with us for it.

Regards,
Murali