MRBS 1.11.4: Limit r/w access to rooms

[TheDude1969]

Hello Community,

is there maybe a way to allow bookings to defined room by membership of an AD security group?

I am using LDAP for authentication and want to use security groups to control access to rooms but was unable to find something about this in the documentation.

Many thanks in advance,
best regards

TheDude

[campbell-m]

You could try using the roles branch, which allows roles to be assigned to users and groups. For each role you can define which rooms and areas are visible, bookable or admin-able.

The code is still under development though and it will also upgrade your database, after which it won't work with 1.11.4. So I recommend you try it out first on a copy of your database.

[KawaMood]

You could try using the roles branch, which allows roles to be assigned to users and groups. For each role you can define which rooms and areas are visible, bookable or admin-able.

The code is still under development though and it will also upgrade your database, after which it won't work with 1.11.4. So I recommend you try it out first on a copy of your database.

Hi there, I have a question concerning this.
If I start to use this role branch now, would I be able to upgrade MRBS when this feature will be part of an official release?

[campbell-m]

Yes, when this feature eventually becomes part of an official release you'll be able to upgrade your installation. In the meantime new features and bug fixes applied to the main branch are also merged with the roles branch.

[coxmunro]

You could try using dagkonferens i stockholm, which allows roles to be assigned to users and groups. For each role you can define which rooms and areas are visible, bookable or admin-able.
The code is still under development though and it will also upgrade your database, after which it won't work with 1.11.4. So I recommend you try it out first on a copy of your database.

Hi there, I have a question concerning this. If I start to use this role branch now, would I be able to upgrade MRBS when this feature will be part of an official release?

I had the same question in my mind, now got the answer. Thanks

[zaid4840]

If you start using the role branch now, you will be able to upgrade MRBS when this feature becomes part of an official release. However, it is recommended to test it on a copy of your database first, as the code is still under development and may upgrade your database in a way that is not compatible with version 1.11.4.

[wohenbushuang]

Hi there, it has been four years after the roles branch established, would you consider to provide an official basical release version first? Maybe done is better than perfect.

[campbell-m]

Well there's nothing to stop you using it - I'm not quite sure what benefit a release brings.

There's still some more work to be done to finish it off. However what I have been considering as an idea is to:

• make a 1.11.6 release of MRBS in the next month or two
• add a configuration setting, eg $enable_roles, to the roles branch which by default is false and makes the roles branch behave in exactly the same way as standard MRBS.
• then merge the roles branch back into main
• then make another release; if you want to use roles just set the config setting to true.

[wohenbushuang]

The code is still under development though and it will also upgrade your database

That's what I'm afraid. Actually I modified this awesome project to adapt with our existing oauth2 authorization system. I'm happy to migrate the oauth2 part based on this role feature in someday when it is kind of "stable" (e.g. a release) meaning this role feature won't be abandon (because of too much dev time cost).

So glad to hear the future milestones and eagerly look forward to them.