Extracting Authorization Code and State from URL and Authenticating User with Stitch

During the meeting, the participants discussed an issue with Weweb and Stitch webhooks. They were trying to retrieve specific information from the webhook, but it was not working as expected. They identified that the problem was related to the use of the get all input function, which only retrieves data from the body, whereas they needed to retrieve data from the URL.

To solve this issue, they discussed creating a new function to extract the required information from the URL. They also discussed the structure of the URL and how to parse the information it contains, such as the authorization code, state, scope, and session state. They verified that the information was visible in the URL and could be accessed through specified inputs in Xano. The participants further discussed how to use this information to authenticate and retrieve tokens from Stitch. They talked about using the state and session state to identify the user and the code verifier for authentication. They mentioned updating the existing functions to incorporate the new inputs and removing unnecessary parameters like auth code and rec state. The participants emphasized the importance of securely handling OAuth and redirecting to a Weweb page after the authentication process. They suggested using a 301 or 302 redirect to ensure a seamless user experience. Overall, the meeting provided insights into the specific issue with Weweb and Stitch webhooks, suggested a solution using specified inputs to retrieve data from the URL, and discussed the necessary steps for authentication and token retrieval.

(Source: Office Hours 12/13 )

State Change Members Can View The Video Here

View This Video Now

Join State Change Risk-Free