Hi all - I am thrilled that I was able to upgrade from booked 2.76 on Debian 9 to the latest LibreBooking 2.85 on Debian 11. I was able to first upgrade the OS and then the LibreBooking "upgrade" method did work. At first, I tried the manual install on Debian 11 and that did NOT work. I traced that down to missing filled in entries in the config.php (causing the "Unknown Error"). Also, the database_schema/create-scheme.sql has one error in it which then prevents the create-data.sql from running. Specifically:
the "CREATE TABLE
layouts" is missing the "layout_type" field.
I am trying to setup SAML authentication for SSO login. I have a very similar problem to @kevin500_gitlab: All the user attributes from the IdP (Azure AD) are obtained, the booked debug log shows:
2022-06-22T12:14:39+02:00  DEBUG default - [User= ()] Logging in with user: auXXXXX [File=/var/www/makerlab/booked/lib/Application/Authentication/Authentication.php,Line=111]
No users are entered into bookeddb.users. After the login process the browser ends up in a redirect loop. The debug log shows the login process over and over.
Pertaining to Kevin's problem: I have activated SQLite, and a file is constructed on the login attempt.
Any idea why I cannot login?
I'm trying to figure out whether the app can support the following use case:
Can such a scenario be implemented on BookedScheduler? Tinkering with the live demo, I wasn't able to figure out a way. Workarounds are also welcome, as long as there's a way to preserve precedence to privileged users.