In the future we should introduce more and more new features as
beta/preview initially, so polishing around this is definitely worth it.
It may also be nice from a usability perspective if we can have some more
advanced features disabled by default as that could help reduce the number
of bells and whistles in the UIs.
On Fri, 8 Nov 2019 at 14:51, Stan Silvert <ssilvert(a)redhat.com> wrote:
I think it makes sense. It's just a matter of whether it's
worth the
effort or not.
It's a really good idea from a marketing perspective. Users would have
a one-stop shop to find the cool new features that are on the way.
On 11/8/2019 1:03 AM, Stian Thorgersen wrote:
> We currently have a mechanism in place to allow features to be marked as
> preview, experimental and disabled-by-default.
>
> Enabling/disabling these features requires restarting the server and also
> it is a global option.
>
> It may be better to instead have these as options on a realm. This would
> allow enabling/disabling such features at runtime, and it would be
possible
> to enable through the admin console directly.
>
> It also has the benefit of allowing certain features only for certain
> realms. For example you may want to enable impersonation only for a
> specific realm, not for all realms. Same with a preview feature you may
> want to enable it in a test realm, not for all realms.
>
> Thoughts?
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev