[keycloak-dev] Applying post-create realm modifications

[Bill Burke]

On 7/20/16 7:11 PM, Dmitry Telegin wrote:
>>
>> +1.  Name the event RealmPostCreateEvent.
>>
>
> OK, so I'll be filing now a JIRA issue and then a PR, right?
>

Yes.

>> I was also thinking of having a FeatureProvider that would be an 
>> "uber" component that could install sub components.  i.e. an 
>> authenticator, user federation provider, etc.
>>
>> Interested in contributing?
>>
>
> Absolutely! This would be a perfect match for what I'm working on now. 
> It's in beta at the moment, but I think a little disclosure won't 
> hurt: it will be a device management add-on that will let KeyCloak 
> manage hardware OTP generators (tokens). It implements full device 
> lifecycle support, including bulk import (from a vendor-supplied XML 
> file), maintaining a pool of available devices, enrollment/revocation 
> etc. Here's a draft manual:
>
> https://dteleguin.gitbooks.io/keycloak-tms-ru/content/
>
> (It's in Russian, so skip the text and look at screenshots, just to 
> have an idea what's it all about.)
>
> Under the hood, it consists of custom JPA entity, custom REST 
> resource, custom authenticator, a customized GUI theme, and a code to 
> tweak newly created realms (hence this discussion). I think extensions 
> like this would definitely benefit from some kind of umbrella 
> construct, or "uber" component. I could even envision it becoming the 
> base for plugin-like architecture and even plugin "market", similar to 
> what we have in Atlassian products.
>

Lets get some requirements going on the FeatureProvider in separate.   
Your devices thing looks interesting too and we should discuss in a 
separate thread.