Re: [bigbluebutton-dev] Greenlight v3 Alpha Released

[Martin Thomas Schrott]

crosspost to dev and greenlight - please reply in the greenlight group!

Hi and thanks for the first GL 3 Version!

some questions on the install instructions:

1. Is it possible to use an existing KC? Should this be done via openid, or can the KC be replaced in the config anyhow?

2. missing links:

"By default, Greenlight ships with Keycloak to provide system administrators an easy way to configure authentication.
To correctly configure Keycloak with your chosen Identity Provider, see Configuring Keycloak.
To connect to another authentication broker through OpenID, see Connecting to Another OpenID Provider.
If don’t plan on using Keycloak, and you would like to completely remove it from your system, see Removing Keycloak."

the links to these sub-instructions are missing or are wrong.

3. db manipulation

as some of our services relie on changing values in the db, is it still possible to change things in the gl db without breaking something? e.g. meeting-id, exchange owners, change roles and so on?

thanks and best regards

Martin

Am 14.09.2022 um 15:33 schrieb 'Ahmad Farhat' via BigBlueButton-dev:

Hi Everyone,

Over the past few months, our team has been working hard to completely re-archictect and re-write Greenlight from scratch using newer technologies and approaches. We are now pleased to announce the release of Greenlight v3 Alpha!

The purpose of this Alpha is to give the community an early opportunity to download v3 and explore the new look and feel of the application. We've also adopted a different approach to installation, which should provide an improved experience for all system administrators.

Greenlight v3 Alpha is *NOT* a production ready application. It contains some missing/incomplete features and should only be used for testing and exploration purposes.

To install Greenlight v3 Alpha, see our docs here.

For any suggestions, notes, encountered issues or questions kindly refer to the Greenlight official repository: http://github.com/bigbluebutton/greenlight/
And the Google community group: https://groups.google.com/g/bigbluebutton-greenlight

Ahmad
--
You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-dev/de47724f-e228-412e-8e36-2315844dce27n%40googlegroups.com.

[ahmad....@blindsidenetworks.com]

Hi Martin,

> 1. Is it possible to use an existing KC? Should this be done via openid, or can the KC be replaced in the config anyhow?

https://docs.bigbluebutton.org/greenlight_v3/gl3-keycloak.html#connecting-to-another-openid-provider

> 2. missing links:

Thanks for the heads up - the links have been fixed.

> 3. db manipulation

Yep - in terms of database structure, v3 is essentially just a more refined version of v2. The commands may differ slightly, but you can still make any changes you'd like to your database

Ahmad

[Martin Thomas Schrott]

Thank you Ahmad!

great :-)

cheers

Martin

You received this message because you are subscribed to the Google Groups "bigbluebutton-greenlight" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-gree...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-greenlight/64cd7986-a184-41cc-a955-f7b3ceb5a776n%40googlegroups.com.

[Martin Thomas Schrott]

Hi Ahmad,


additionally some notes:

> > 1. Is it possible to use an existing KC? Should this be done via
> openid, or can the KC be replaced in the config anyhow?
>
> https://docs.bigbluebutton.org/greenlight_v3/gl3-keycloak.html#connecting-to-another-openid-provider
>

1. in this guide there are some instructions presented as images. This
is not accessible for users with screenreaders. It would be very good if
these instructions (mainly lines to be removed) could be given as text
so anybody can access this information.


2. would it be possible to provide a second (or third) docker-compose
template that allows setting up GL with KC, without KC or with OID - so
the removal of lines must not be done manually ... maybe this would help
to minimize support requests due to users, that did not find
instructions or are missing some steps / do something wrong.


just my thoughts ;-)

all the best


Martin

[ahmad....@blindsidenetworks.com]

Hi Martin,

Thank you for the feedback. The pictures are just there as an additional help - they don't provide any information that isn't specified in the text itself. 

As for the docker-compose, that is a good idea - we'll see if we can work out some time to get that done

Ahmad

[Martin Thomas Schrott]

Hi Ahmad

> Thank you for the feedback. The pictures are just there as an
> additional help - they don't provide any information that isn't
> specified in the text itself.
>

not really ;-)

see:

"Then, remove the Keycloak service from the docker-compose.yaml file as
follow by removing all of the highlighted lines:
Remove Compose graphic"


I cannot see which lines should be removed.

hth

cheers

Martin