You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
System:
BBB 2.6.0 / GL 3.0.1 with external KeyCloak and User Federation against our Active Directory using Kerberos authentication. 'Require users to be signed in before joining' is 'Force enabled', so no anonymous users in the system.
The button 'Sign up' on the top of the GL screen is obsolete (users are always added to the Active Directory another way), but I can't remove this button. Is there a way, a hidden .env parameter or similar, or could this be implemented?
Using Kerberos authentication with KC is very handy, because from the user's perspective there's no need to login manually or entering any credentials. It would be extremely useful, if there was some kind of 'auto login' parameter, so anyone accessing a GL page not being authenticated would automatically be so via KC. At the moment, people have to manually click either on 'Sign in' or 'Sign up', which is annoying and misleading to many users.
TIA
The text was updated successfully, but these errors were encountered:
System:
BBB 2.6.0 / GL 3.0.1 with external KeyCloak and User Federation against our Active Directory using Kerberos authentication. 'Require users to be signed in before joining' is 'Force enabled', so no anonymous users in the system.
The button 'Sign up' on the top of the GL screen is obsolete (users are always added to the Active Directory another way), but I can't remove this button. Is there a way, a hidden .env parameter or similar, or could this be implemented?
Using Kerberos authentication with KC is very handy, because from the user's perspective there's no need to login manually or entering any credentials. It would be extremely useful, if there was some kind of 'auto login' parameter, so anyone accessing a GL page not being authenticated would automatically be so via KC. At the moment, people have to manually click either on 'Sign in' or 'Sign up', which is annoying and misleading to many users.
TIA
The text was updated successfully, but these errors were encountered: