Skip to main content
10 events
when toggle format what by license comment
Mar 22, 2018 at 18:36 vote accept Olivia
Mar 22, 2018 at 15:53 comment added BritishBoyinDC I haven't pushed it live yet, but it seemed like a more solid approach so we'll see...
Mar 22, 2018 at 15:19 comment added Olivia Awesome thanks, one last question - do you feel that Auth.JWT is an easier way to go? Which way do you like better?
Mar 22, 2018 at 15:01 comment added BritishBoyinDC That's the approach we we've used and it has worked fine for us
Mar 22, 2018 at 14:55 comment added Olivia okay great, the google user shouldn't change ever, so I need a one time authorization in chrome console, save the refresh token, and from there I can call for the refresh token every time the access token is expired?
Mar 22, 2018 at 14:52 comment added BritishBoyinDC We just used the same google user to get the analytics data and it is still working fine, several years later...so you'd only need the UI available if that google user might change at some point?
Mar 22, 2018 at 14:46 comment added Olivia So once we get a refresh token from one person and save it, will I ever need another refresh token again (even if multiple people are using the google api)? And to me this means that we do, in fact, need the UI at some point to be able to authorize. Is this correct?
Mar 22, 2018 at 14:17 comment added BritishBoyinDC So from what I remember, you do the first part (steps 1-4 ) in the Google Console and save the refresh token from that flow. That way, you should just need to store the Refresh Token along with Secret and Id in your setting in SFDC As long as the refresh token is valid, you can use it to get a new access token in your code without needing to do the authorization piece again
Mar 22, 2018 at 14:12 comment added Olivia when you say this should work- if I remove the redirect URL, how will I obtain the authorization code? And then how would I save it to a custom setting?
Mar 22, 2018 at 13:18 history answered BritishBoyinDC CC BY-SA 3.0