Archived from the Bravo community forum (2021–2026). Some answers may refer to older versions of Bravo.
I'm having trouble getting 422 error when trying to login?
It was working previously. I'm trying to implement user_id filters and it stopped working.
I removed everything I modified (not much) but it's still giving me this error?
I can create a new account and I get the same error.
All of my endpoints test correctly when using Bravo's API Requests, and of course they work in Xano as well.
Also, I thought page:login and action:logout were in the master list? I only see Oath and firebase now?
Is Xano custom login still supported? Are there other login options, like login:once or something I could try that also work with Xano? And how long is the Authtoken set for? Can I change it's life?
2 replies
Hi, i can confirm - my login with Xano backend is working at the moment and i use [page:login] tag;
From my experience xano authorization essentials are:
- API Xano collection settings choose Bearer and leave token empty
- On POST Login endpoint setting variable
- On binding page setting response action to set access token as a variable. On figma desing it is [action:login] tag
And what was super confusing for me i needed to set _authorization test value instead of variable name like in all other cases. this was the only way to test calls from bravo to work
Hey all, thought I updated this here, in my case, my issue was I started setting all of my variables to match the keys, that lead me to having my variable for the get user info from Xano as user_id when you do this it breaks the authentication, you have to keep that set to id only. or that green arrow goes away. That was my issue.
Wrote something in this thread and want it removed? Request removal
Ask the community on Discord
This archive is read-only. New questions, office hours and product updates now happen in the Bravo Discord.
Join the Discord