Re: [keycloak-dev] 1.2.beta1 planning, need you to defer things
On 3/12/2015 1:40 AM, Stian Thorgersen wrote:
I'd like to reopen KEYCLOAK-311 as IMO it's not solved. This
is not referring to the claim mapping work you've done, it's something else.
I opened two jiras. One, a "claim validation" jira and another
broker->Usermodel mappers. That should have covered what 311 is not doing.
Before we can do a release we need to make sure that database
migration works (I know they don't atm as social providers and social links are lost).
We also need to add transformation of JSON exports and representations so older versions
can be imported into 1.2.0.Beta1.
Not sure, but json imports from older versions should be backwards
compatible. We're just doing migrations via json export/import right?
>
> I'm going to try and close existing bugs and implement features needed
> for jboss.org guys over the next 2 weeks as well as test out master to
> make sure things still work.
With regards to jboss.org guys we shouldn't just add features because they request
it. Take for example KEYCLOAK-1045, which was easily solved with we already have. Another
one is KEYCLOAK-1051, which I think is a horrible idea.
I don't want to just add features either, but some of their things are
valid...i.e. finding out if a user is logged and who they are without
doing all the token stuff.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com