You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If your application is using a different Flow instance to obtain the token, you will need to specify the state when constructing the Flow.
However, there is no obvious way to actually specify that state when constructing that Flow, because there is no state argument/parameter on any Flow constructor or factory (such as Flow.from_client_config). Simply passing the state as a named parameter to fetch_token doesn't do what is expected either.
Describe the solution you'd like
Please update the documentation to show how a state (as returned by authorization_url) would be fed into a new Flow instance.
The text was updated successfully, but these errors were encountered:
D'oh, answered my own question with some further digging. The state parameter is ultimately consumed by OAuth2Session, as already explicitly stated in the docs. Sorry.
Is your feature request related to a problem? Please describe.
I need to get run
Flow.fetch_token
on a differentFlow
instance than the one I used to get theauthorization_url
.The docs for
authorization_url
say that astate
is returned, and:However, there is no obvious way to actually specify that
state
when constructing thatFlow
, because there is nostate
argument/parameter on anyFlow
constructor or factory (such asFlow.from_client_config
). Simply passing thestate
as a named parameter tofetch_token
doesn't do what is expected either.Describe the solution you'd like
Please update the documentation to show how a
state
(as returned byauthorization_url
) would be fed into a newFlow
instance.The text was updated successfully, but these errors were encountered: