[keycloak-user] UI for custom providers

[Tomás García]

Thanks for the explanation, Bill.

I guess there's no point on opening an issue to propose what I said, right?

On Mon, Mar 13, 2017 at 5:34 PM Bill Burke <bburke at redhat.com> wrote:

> There's 2 types of configuration:
>
> * Config for the ProviderFactory.  This is for the entire Keycloak
> instance.  We do not support configuring this through admin console as
> this configuration applies to ALL REALMS managed by the keycloak server.
>
> * Config for Provider instances created.  This depends on the provider.
>
> These SPIs can generically render configuration for Provider instances
> in the admin console:
>
> * User Storage SPI
>
> * Mapper SPIs (broker and clients)
>
> * Authentication SPI config
>
> * Key management
>
> Unfortunately, they all use a little bit different mechanism. User
> Storage SPI and Key management SPI do use the new Component SPI.  Other
> SPIs will eventually be ported to use the generic mechanism.
>
>
> On 3/13/17 12:56 PM, Tomás García wrote:
> > Hi,
> >
> > I wonder if it's planned to add the possibility to make UI (HTML) for a
> > custom provider, like having a Providers section in the Keycloak
> dashboard
> > menu where it will appear all of those providers with custom UI. For
> > example, for an Keycloak custom API I've made, I want to let the admin to
> > change a whitelist of clients used inside the provider. Right now, I'll
> > have to use the configuration stuff inside the standalone.xml file, which
> > means that the server must be reset each time.
> >
> > In this issue (https://issues.jboss.org/browse/KEYCLOAK-3605), Stian you
> > said:
> >
> > "I think you misunderstood me. We now have a generic component storage
> > mechanism that makes it easy to add configurable providers. It sorts out
> > persistence as well as UI automatically. To support that the Email Sender
> > SPI including UI screens have to be changed. IMO that should be done
> prior
> > to adding more options to the email sender. "
> >
> > Is this generic component storage mechanism going in this direction? Is
> > there an explanation somewhere about this mechanism? Example code?
> >
> > Thanks.
> > _______________________________________________
> > keycloak-user mailing list
> > keycloak-user at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/keycloak-user
>
> _______________________________________________
> keycloak-user mailing list
> keycloak-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-user
>