[go-nuts] Re: The Trouble With Tokens (Refresh Tokens, that is...)

2018-02-20 Thread Andrew Watson
I fixed my problem myself. It turns out the app that consumes the tokens also needs to load the oauth2 config with client id, secret etc. I did not know this! On Tuesday, February 20, 2018 at 4:11:09 PM UTC-5, Andrew Watson wrote: > > So, I built something that uses the 3 step OAuth 2.0

[go-nuts] Re: Go 1.10 is released

2018-02-20 Thread Andrew Watson
Awesome! I discovered this by accident because I was upgrading my MBP via homebrew expecting a 1.9.x version and it came up with 1.10! On Friday, February 16, 2018 at 2:36:22 PM UTC-5, Andrew Bonventre wrote: > > Hello gophers, > > We just released Go 1.10. > > You can read the announcement blog

[go-nuts] Re: Golang HTTP POST handling

2018-02-20 Thread Andrew Watson
You should, of course, consider adding some rigor such as CSRF protection to that form! I'd suggest something like http://www.gorillatoolkit.org/pkg/csrf for that! On Tuesday, February 20, 2018 at 11:16:57 AM UTC-5, Sankar wrote: > > Hi, > > I have a Golang HTTP server which is consumed by mobi

[go-nuts] The Trouble With Tokens (Refresh Tokens, that is...)

2018-02-20 Thread Andrew Watson
So, I built something that uses the 3 step OAuth 2.0 Dance to get access to gmail. It stores the OAuth tokens after encrypting them with Vault transit keys and then I built something that decrypts those tokens, constructs an OAuth 2.0 client using them and goes looking for things in my inbox.