I am using the Xano Authentication to log my user in. There is no issue at all on the weweb editor but for some weird reason, I can log in when I test it on the staging environment neither can I do it on production.
Here is my workflow on my log in page:
user provides credentials
Xano plug in authenticate my user
I then have a split to redirect my users to the right page (I have 3 different user types)
On staging (or production), I can see that the requests to Xano are correctly done and the responses on Xano are all 200 responses but for some weird reason the redirection to my page does not happen I can’t even log in
Is there anything you remember changing in your project in the meantime? Even something that seems unrelated might help. No worries if nothing comes to mind! We’ll keep investigating anyway
Well for me the issue is still there. I’m not able to log in at all. The issue is not in the editor though, it’s when I try to test my log in on staging or prod. See attached.
Yes, the bug is still open. The tech team is looking into it. If you want to send me a link to your project in a direct message, I’ll add it to the bug ticket to give additional context to the devs.
We make it work in the editor to help you build without blockers but it comes with this type of downsides. The product team is aware but we haven’t quite found the perfect approach yet. Work in progress!
This is fixed for me as of today. Not sure if something was changed on Weweb’s end, but simply publishing the app once again resolved it (while yesterday it didn’t).
Hi, I looked at your project, it seem you’re using groups with multiple roles but your users can only have one role because its a type text column. Our group use an AND logic, it mean your user need to have every roles included in the group to match it.
To have a OR logic you have to create a different group for every role (yes it can seem redundant) and apply multiple groups in the page, the different groups will be handled with a OR logic at the page level.
Tell me if it help you to fix your issue, because I was not able to reproduce it on my side.
Hi Alexis, thanks for your reply. Keeping it to one role per group does indeed solve the issue. For some reason I hadn’t noticed the And operator in the group config.
As you point out, it does feel redundant in certain structures of permissions. Do you plan on supporting an Or operator as well?
Not planned for now as the current system allow you to implement both logic and never was a blocker for anyone, but yeah in a long term it could be improved so you can choose the logic you want on the group (And even use multiple user attributes and conditions to compose your own rules )
)