----- Original Message -----
From: "Marek Posolda" <mposolda(a)redhat.com>
To: "Stian Thorgersen" <stian(a)redhat.com>, "keycloak-dev"
<keycloak-dev(a)lists.jboss.org>
Sent: Tuesday, 12 May, 2015 10:47:54 AM
Subject: Re: [keycloak-dev] Private/public SPIs
No objection. Does private have any limitation from the implementation
perspective or is it just a marker? Will user be still able to implement
some private SPI and put it into 'providers' folder?
Just a marker - maybe we'll add a log warn if someone registers their own provider for
a private SPI, but nothing beyond that
Marek
On 12.5.2015 08:24, Stian Thorgersen wrote:
> To make it easy to identify which SPIs are public I've added isPrivate
> method to SPI.
>
> The list below is all the SPIs we currently have, any objections to which
> are marked as private?
>
>
> SPI Private
> -------------------------------------
> account true
> client-import true
> connectionsFile true
> connectionsHttpClient true
> connectionsInfinispan true
> connectionsJpa true
> connectionsJpaUpdater true
> connectionsMongo true
> connectionsMongoUpdater true
> email true
> eventsListener false
> eventsStore true
> export true
> identity-provider-mapper false
> identity_provider false
> import true
> login true
> login-protocol true
> migration true
> protocol-mapper false
> realm true
> realmCache true
> social false
> theme true
> timer true
> user true
> userCache true
> userFederation false
> userSessions true
> well-known true
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev