Supported environments
by Stian Thorgersen
For 1.2.0.Final the server should be deployable to:
* WildFly 8.2.0.Final
* EAP 6.4.0.GA
After 1.2.0.Final we should move on to WildFly 9.0.0.Final (once it's released). As APIs has changed, and there's also new features in WF 9 we can leverage, the cleanest way to do this is to drop support for deploying to EAP 6.4.0.GA.
With regards to adapters what versions should we support:
* AS7 - can we drop this?
* WildFly - only last (9.0.0.Final) or two last (8.2.0.Final and 9.0.0.Final)?
* EAP - only last (6.4), two last (6.3, 6.4) or three last (6.2, 6.3, 6.4)?
9 years, 4 months
Distribution changes
by Stian Thorgersen
I've pushed a fair amount of changes to the distribution:
* Release is built with "mvn -Pjboss-release install" now as this is consistent with jboss-parent. Also this builds javadoc as well now, so no need to run those separate.
* distribution/examples - a zip with all the examples
* distribution/server-overlay - a zip that can be extracted into an existing WF 8.2.0.Final to install KC, includes docs. Currently it contains server*.xml all with KC enabled, but I was thinking we should just have standalone-keycloak.xml instead
* distribution/server-dist - a zip with WF 8.2.0.Final + server-overlay
* distribution/server-bundle - a bundle with server and examples zip, this should at some point be changed to a dl with demo preloaded onto it
* adapter dists are moved into distribution/adapters, just to clean it up a bit
* Started updating docs, but there's a bit more work to review/update it to make sure it matches updated dists
9 years, 4 months
account theme unfinished?
by Bill Burke
Master was broken. It could not load the account theme as its parent
was still patternfly. I fixed it, but it seems that the account theme
is still the old style. Not sure if you meant to change it to the new
black styling the admin and login pages have.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
9 years, 4 months
apache http client changes
by Bill Burke
Because we have incompatibilites and linkage errors with Apache HTTP
Client in WIldfly I did the following changes:
* I created an Apache HTTP Client "connections provider" module which
outgoing server connections now use.
* This provider is configured in keycloak-server.json and documentation
is in docbook for it.
* Outgoing HTTP requests no longer use Resteasy ClientRequest.
Things to do:
* We need stress tests for backchannel logouts and other
ResourceAdminManager requests. Broker and admin console. Now that an
HttpClient instance is only created once at boot time instead of per
request, we need to make absolutely sure connections are being cleaned up.
* I need to test backchannel and ResourceAdminManager requests with
SSL/HTTPS.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
9 years, 4 months
"Direct grants only" switch broken in admin console
by Marek Posolda
The "Direct grants only" switch doesn't seem to work in admin console in
Clients screen. It doesn't hide redirect URI and value is not persisted
(it's always off).
Recently we discussed to convert it into combobox of 3 states:
1) Direct grants only, which hides redirect URI
2) Direct grants enabled
3) Direct grants disabled
but I am not sure if we agree on it.
Maybe for RC1 we can just hide the switch from UI and then for
1.2.0.Final we can properly fix it and convert it into the combobox.
What do you think?
Marek
9 years, 4 months
generic model migration
by Bill Burke
I implemented this as a singleton data item in JPA or Mongo or File. I
jsut store the current version. Implementation is in
MigrationModelManager and it just checks the currently stored version
versus the deployed version. Its all hardcoded at the moment, but does
give some abstraction. I think it is good enough going forward. Don't
need anything fancy.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
9 years, 4 months
