Archived from the Bravo community forum (2021–2026). Some answers may refer to older versions of Bravo.
UPD: The issue was solved by refactoring the API collection, like in the tutorial: https://docs.bravostudio.app/integrations/user-authentication/authentication-with-custom-backend
Hello, dear community.
I've faced the issue that arrived not a long time ago. When creating a new user for testing I have my requests giving 401 errors like auth token not saved in Bravo.
It's weird because with my ordinary user all work well. I thought that I didn't set up headers correctly, but no:
![CleanShot 2022-12-13 at [email removed]](https://cdn.sanity.io/images/mou08vec/production/8498d246df5f4773c4770cee9d168e776f3ef163-1510x402.png)
In Xano it's showing that auth token hasn't been sent
![CleanShot 2022-12-13 at [email removed]](https://cdn.sanity.io/images/mou08vec/production/02b51654383e6715f5b439f4d8b58ca6241f016a-926x906.png)
And in one request Bravo is sending token
![CleanShot 2022-12-13 at [email removed]](https://cdn.sanity.io/images/mou08vec/production/2db1fa57615784b2b9f20f033e907827701c9fda-960x1302.png)
And on the next one - not
![CleanShot 2022-12-13 at [email removed]](https://cdn.sanity.io/images/mou08vec/production/892ba32357d7fb959483953667a89908072d568a-976x1242.png)
On Bravo side, both of these requests are having the token
![CleanShot 2022-12-13 at [email removed]](https://cdn.sanity.io/images/mou08vec/production/b5cc8548459eba7830c2c3cf433443d1e23be51d-1458x724.png)
![CleanShot 2022-12-13 at [email removed]](https://cdn.sanity.io/images/mou08vec/production/c0a1299827bba52b11a2ca5a0776b399dd546ea6-1470x712.png)
14 replies
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![CleanShot 2022-12-13 at [email removed]](https://cdn.sanity.io/images/mou08vec/production/5a46558d7892cf82eeec91eafff6208a6420f9aa-1018x422.png)