Everything was working well, untill a two weeks ago. I logged into weweb and somehow my settings for the Xano auth plugin where empty. I created a new API token in Xano and set up authentication, but I haven’t been able to successfully log in since.
I see “withCredentials: true” meaning you probably toggled the option “send credentials” but this option require a particular setup on xano side, please toggle off this option, it’s only useful to send custom cookie.
I removed your screenshot as it contained sensitive informations
1 Like
Did this solve your problem? I’m facing the same issue and have with credentials off. Was able to use the xano demo website to log in with twitter fine. Simply can’t do it with weweb?
This is a snip of my error response. I have the callback url as my weweb editor url as well
So dug into this further, I noticed that the request in the log report from Weweb shows that xano is providing an additional slug to the redirect url. For example, my home editor weweb url is https://editor.weweb(dot)io/b7591ea4-08de-4af2-99fb-6edd718e51f8 however the request in weweb shows this url: https://x8ki-letl-twmt.n7.xano(dot)io/api:CJaexNTY/oauth/twitter/request_token?redirect_uri=https:%2F%2Feditor.weweb.io%2Fb7591ea4-08de-4af2-99fb-6edd718e51f8%2F3517ae00-5cc0-4a6f-bd79-418df8faf85e"
When I change the callback url in twitter to the longer editor weweb url xano is creating, the twitter window pops up, I authorize, and I’m redirected to weweb, however my authentication is still false and no new record is created in xano
Thank you for that. I am using the Xano Auth plugin and I cannot find how to toggle the send credentials option.
Should be in your workflow for logging in
The short one is your editor link and fallback to your homepage, the longest one include the path of the specified page, you should authorise and use the longest one in your auth provider setting (because when we let you select a redirection page, it’s the longest one that is used)
You can create a ticket on support.weweb.io if you need us to check your setup, please include as many information as possible
It could be located in your plugins configurations, there is a global option in the step Global Headers, in both xano and xano auth