I'm happy to push for this if you think we can still deliver 1.0.final in a reasonable
time.
Can we do this in stages? First split ModelProvider into RealmProvider and UserProvider,
update cache etc. Then start work on this in a branch? So we can roll 1.0.final without it
if it turns out to take to long to delivery?
Would be good to have a Hangout again next week to discuss the next steps!
----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: "Stian Thorgersen" <stian(a)redhat.com>, "Marek Posolda"
<mposolda(a)redhat.com>
Cc: keycloak-dev(a)lists.jboss.org
Sent: Friday, 11 July, 2014 3:12:41 PM
Subject: Re: [keycloak-dev] sync/federation requirements/ideas
On 7/11/2014 9:05 AM, Stian Thorgersen wrote:
> This sounds like exactly what we need. There are quite a lot of kinks to
> work out though.
>
My vote is we fix AuthProvider and sync now. Do another iteration.
Users *really* want this. You're right, there's a lot of kinks we need
to work out, but we don't want a large set of users we have to move off
of an existing SPI.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com