Re: v201705 Authentication

2017-06-20 Thread Sergiu Obreja
Hello! I'm using web application flow. I've managed to make it work. After the log in into the consent screen I'm redirected back to my page and I get a refresh token which I store in my database. Anytime I want to connect again on the behalf of that specific user I'm adding the refresh token t

Re: v201705 Authentication

2017-06-15 Thread Sergiu Obreja
Hi, I already have a refresh token generated based on my client id and client secret that's stored in the .ini file, but what's confusing me is that after logging through a consent screen after I get the code I am redirected back to my page and I get a different refresh_token. -- -- =~=~=~=~

Re: v201705 Authentication

2017-06-14 Thread Sergiu Obreja
Hi Peter! The problem is that I don't know how to make the call using the access token and the refresh token I already have. Thanks! -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+G

v201705 Authentication

2017-06-13 Thread Sergiu Obreja
Hello guys! I'm working on an web application where clients can connect their AW account and get reports. Until now I was using v201607 with OAuth2 and offline access and for each user I was saving the access token and the refresh token... all was working like a charm. Now I'm upgrading to v201