https://groups.google.com/g/adwords-api/c/bAgqtTr5OoY
This issue has branched into a follow up question that should probably be 
handled separately.

I'm investigating the process of requesting refresh tokens. I use the 
client library for Python titled "generate_user_credentials.py" for Desktop 
app flow. In truth, the app is just querying data from Ads and using it for 
internal reporting.

The library spins up a server that waits for a callback with a string query 
specifying:
1. state
2. code
3. scope

State and Scope are easy to get, as they're provided in the original oauth 
link used to authenticate. Code is much more difficult to reproduce, though 
it seems that you guys actually generate that on your end and send back in 
one of the page's POST requests.

So I investigated that POST request, which goes to 
"https://accounts.google.com/signin/oauth/consent/approval";. It appears to 
require the following:
*params:*
1. authuser
*headers:*
1.Content-Type
2.Cookie
*payload:*
f.req = some_array
at = some_string

Most of these seem to be constants, but I am struggling with the *some_array 
*and *some_string* values.

*some_array *contains a token that begins with "!ChR" + a ' ∙ ' separator 
for a second value, and I can not reproduce it so far. It must be generated 
client-side, as I have checked all incoming data for this token and can not 
find it. I have the feeling it's a hash of something else, but when 
reviewing the javascript I was completely lost. I don't know javascript, so 
it's difficult to read (on top of there being A LOT of js to sort through).

I haven't gotten to the *at *variable that contains its own token yet, but 
I'll need to understand how this is generated as well.

Can someone help me get to a point where I can reproduce the token 
beginning with "!ChR"? Also the value for "at" in the payload.

Thank you

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/c6b6ad5b-f3db-451f-b0e0-054dafa42ce7n%40googlegroups.com.

Reply via email to