-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility of this plugin with Greenlight_v3? #3
Comments
Hi Florian, Honestly, I am not sure as I haven't had the time to migrate our small BBB instance to the latest Greenlight version. However, based on the external authentication documentation and the Greenlight issue #4817 I am not sure if LDAP is even supported anymore without an additional provider in the middle. I tried to verify this by grepping Greenlight's code and git history, where all references to LDAP disappeared starting on Without having tested anything yet, I would try to recommend setting up some KeyCloak with LDAP as its back end, resulting in another block on this already huge software stack. With the fundamental difference between Greenlight 2 and Greenlight 3, this very software will not work directly with Greenlight 3 as it has changed it's database layout. However, I am optimistic that this hacky tool won't be needed anymore. But please give me some time to verify this and be a bit patient, because it's currently not on top of my to do list. If you have had any findings in the meantime, please feel free to report them in this issue. Cheers, |
Hi Alvar,
thanks for the information.
I didn’t even know they chucked LDAP-Auth in favor of Keycloak.
I found this thraed discussing the issue:
bigbluebutton/greenlight#4817
They suggest hooking up the keycloak service directly to the LDAP-server.
Seems you need to change a few DB fields to get it to work
As of right now I have no idea if this setup will be able to synch changes from the LDAP system.
I will look into this in the coming days.
Regards
Florian
…-----Ursprüngliche Nachricht-----
Von: alvar ***@***.***>
Gesendet: Mittwoch, 14. Juni 2023 12:50
An: oxzi/greenlight-ldap-sync ***@***.***>
Cc: Seifer, Florian ***@***.***>; Author ***@***.***>
Betreff: Re: [oxzi/greenlight-ldap-sync] Compatibility of this plugin with Greenlight_v3? (Issue #3)
Hi Florian,
Honestly, I am not sure as I haven't had the time to migrate our small BBB instance to the latest Greenlight version.
However, based on the external authentication documentation <https://docs.bigbluebutton.org/greenlight/v3/external-authentication> and the Greenlight issue #4817 <bigbluebutton/greenlight#4817> I am not sure if LDAP is even supported anymore without an additional provider in the middle. I tried to verify this by grepping Greenlight's code and git history, where all references to LDAP disappeared starting on release-3.0.0-beta.4.
Without having tested anything yet, I would try to recommend setting up some KeyCloak with LDAP as its back end, resulting in another block on this already huge software stack.
With the fundamental difference between Greenlight 2 and Greenlight 3, this very software will not work directly with Greenlight 3 as it has changed it's database layout. However, I am optimistic that this hacky tool won't be needed anymore. But please give me some time to verify this and be a bit patient, because it's currently not on top of my to do list.
If you have had any findings in the meantime, please feel free to report them in this issue.
Cheers,
Alvar
—
Reply to this email directly, view it on GitHub <#3 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARJ7MVAT7BQTXKVB7RJKP6TXLGJN7ANCNFSM6AAAAAAZDGAH3I> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/ARJ7MVBDTASL2Z7ZOQSOVZ3XLGJN7A5CNFSM6AAAAAAZDGAH3KWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS62QJ2S.gif> Message ID: ***@***.***>
|
Hi,
I just realized you suggested the exact same issue, nice to see we're on the same page! 😉
Cheers!
…-----Ursprüngliche Nachricht-----
Von: alvar ***@***.***>
Gesendet: Mittwoch, 14. Juni 2023 12:50
An: oxzi/greenlight-ldap-sync ***@***.***>
Cc: Seifer, Florian ***@***.***>; Author ***@***.***>
Betreff: Re: [oxzi/greenlight-ldap-sync] Compatibility of this plugin with Greenlight_v3? (Issue #3)
Hi Florian,
Honestly, I am not sure as I haven't had the time to migrate our small BBB instance to the latest Greenlight version.
However, based on the external authentication documentation <https://docs.bigbluebutton.org/greenlight/v3/external-authentication> and the Greenlight issue #4817 <bigbluebutton/greenlight#4817> I am not sure if LDAP is even supported anymore without an additional provider in the middle. I tried to verify this by grepping Greenlight's code and git history, where all references to LDAP disappeared starting on release-3.0.0-beta.4.
Without having tested anything yet, I would try to recommend setting up some KeyCloak with LDAP as its back end, resulting in another block on this already huge software stack.
With the fundamental difference between Greenlight 2 and Greenlight 3, this very software will not work directly with Greenlight 3 as it has changed it's database layout. However, I am optimistic that this hacky tool won't be needed anymore. But please give me some time to verify this and be a bit patient, because it's currently not on top of my to do list.
If you have had any findings in the meantime, please feel free to report them in this issue.
Cheers,
Alvar
—
Reply to this email directly, view it on GitHub <#3 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARJ7MVAT7BQTXKVB7RJKP6TXLGJN7ANCNFSM6AAAAAAZDGAH3I> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/ARJ7MVBDTASL2Z7ZOQSOVZ3XLGJN7A5CNFSM6AAAAAAZDGAH3KWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS62QJ2S.gif> Message ID: ***@***.***>
|
Hello Alva,
as the title suggests, do you have any idea if your synch-plugin is compatible with the new version of Greenlight?
Regards,
Florian
The text was updated successfully, but these errors were encountered: