2:27 p.m.
What will the distribution of Keycloak be for M1? Just keycloak-server.war? Should this be
deployable to AS 7.1.1.Final and WildFly?
OpenShift QuickStart
--------------------
For OpenShift I thought a QuickStart using the AS 7.1.1.Final cartridge would be the
simplest option. The QuickStart basically is a github repo that contains a starting point
to get Keycloak installed. It would update the Resteasy version + install
keycloak-server.war. To start a Keycloak instance using rhc you'd use:
# rhc app-create keycloak jbossas-7 --from-code
https://github.com/keycloak/keycloak-openshift-quickstart.git
We could also make the QuickStart automatically configure Keycloak to use PostgreSQL if
available. For example if creating a Keycloak instance with the following it would use
PostgreSQL instead of H2:
# rhc app-create keycloak jbossas-7 postgresql-9.2 --from-code
https://github.com/keycloak/keycloak-openshift-quickstart.git
WildFly
-------
I've tried to run Keycloak on WildFly and ran into a PicketLink/Hibernate issue (see
https://issues.jboss.org/browse/KEYCLOAK-135 for details). PicketLink guys have merged
fix, but that would require upgrading to 2.5.3.Final when it's released.
I've also tried to upgrade to PicketLink 2.5.2.Final, but am having some issues with
the ApplicationData/Entity. When loading the Application from the database, PicketLink
tries to set a RealmData on ApplicationData.resourceUser which you may imagine throws an
exception. I've added it to https://github.com/stianst/keycloak/tree/pl-2.5. It's
either a bug in PicketLink, or a mistake in ApplicationData/Entity, I'm not sure which
though.
3:08 p.m.
I wanted the distro to be AS7 or Wildfly distro, not just a war. All
preconfigured with SSL, DB, etc. An appliance. Would be cool to
auto-gen a new key-pair for SSL on initial startup, but not sure how
feasible that is.
If I had to pick one or the other, distro should take priority over
Openshift, but we should be able to do both.
Also, not sure how much it makes sense to ship a Wildfly distro without
a Wildfly application adapter. I only partially implemented it a few
months ago. It on the short list for my todo list.
I kind of want picketlink gone so we don't have to deal with the
bullshit you're dealing with. We'll hook it back in for LDAP, et. al.
That would require building a backend for it though so probalby can't
get rid of it for M1.
We still have like 30+ other open issues, btw... We're still missing a
few admin things too.
On 10/30/2013 3:27 PM, Stian Thorgersen wrote:
What will the distribution of Keycloak be for M1? Just
keycloak-server.war? Should this be deployable to AS 7.1.1.Final and WildFly?
OpenShift QuickStart
--------------------
For OpenShift I thought a QuickStart using the AS 7.1.1.Final cartridge would be the
simplest option. The QuickStart basically is a github repo that contains a starting point
to get Keycloak installed. It would update the Resteasy version + install
keycloak-server.war. To start a Keycloak instance using rhc you'd use:
# rhc app-create keycloak jbossas-7 --from-code
https://github.com/keycloak/keycloak-openshift-quickstart.git
We could also make the QuickStart automatically configure Keycloak to use PostgreSQL if
available. For example if creating a Keycloak instance with the following it would use
PostgreSQL instead of H2:
# rhc app-create keycloak jbossas-7 postgresql-9.2 --from-code
https://github.com/keycloak/keycloak-openshift-quickstart.git
WildFly
-------
I've tried to run Keycloak on WildFly and ran into a PicketLink/Hibernate issue (see
https://issues.jboss.org/browse/KEYCLOAK-135 for details). PicketLink guys have merged
fix, but that would require upgrading to 2.5.3.Final when it's released.
I've also tried to upgrade to PicketLink 2.5.2.Final, but am having some issues with
the ApplicationData/Entity. When loading the Application from the database, PicketLink
tries to set a RealmData on ApplicationData.resourceUser which you may imagine throws an
exception. I've added it to https://github.com/stianst/keycloak/tree/pl-2.5. It's
either a bug in PicketLink, or a mistake in ApplicationData/Entity, I'm not sure which
though.
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
9:50 a.m.
I've committed something for this now. I added a server war module, and a dist module.
If you build the project with "-Prelease" it will create a standalone Keycloak
server in dist/target. At the moment it is built on-top of AS 7.1.1.Final.
Currently the database is not configured and it's just using the example datasource
(H2 in-mem, so data is lost on restart).
----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Wednesday, 30 October, 2013 8:08:35 PM
Subject: Re: [keycloak-dev] Keycloak M1 distribution
I wanted the distro to be AS7 or Wildfly distro, not just a war. All
preconfigured with SSL, DB, etc. An appliance. Would be cool to
auto-gen a new key-pair for SSL on initial startup, but not sure how
feasible that is.
If I had to pick one or the other, distro should take priority over
Openshift, but we should be able to do both.
An OpenShift QuickStart is really not that much work. We can base it on
https://github.com/stianst/openshift-wildfly, make it dl Keycloak dist instead of WildFly
dist, add some magic around db config. Should be less than a days work.
Also, not sure how much it makes sense to ship a Wildfly distro without
a Wildfly application adapter. I only partially implemented it a few
months ago. It on the short list for my todo list.
At the moment there's blockers for being able to use WildFly, the adapter and issues
with PicketLink. Besides, it's only a beta at the moment, so I don't think
it's to unreasonable that we ship M1 with AS 7.1.1.Final.
I kind of want picketlink gone so we don't have to deal with the
bullshit you're dealing with. We'll hook it back in for LDAP, et. al.
That would require building a backend for it though so probalby can't
get rid of it for M1.
We still have like 30+ other open issues, btw... We're still missing a
few admin things too.
Can you make sure admin issues are in JIRA? That'll make it easier for Alexandre and
Villiam to work on them. Also, would be good to have some components added to the Keycloak
project in JIRA (at the top of my head, something like: admin, core, services, build,
forms, tests, social, adapters?).
On 10/30/2013 3:27 PM, Stian Thorgersen wrote:
> What will the distribution of Keycloak be for M1? Just keycloak-server.war?
> Should this be deployable to AS 7.1.1.Final and WildFly?
>
> OpenShift QuickStart
> --------------------
>
> For OpenShift I thought a QuickStart using the AS 7.1.1.Final cartridge
> would be the simplest option. The QuickStart basically is a github repo
> that contains a starting point to get Keycloak installed. It would update
> the Resteasy version + install keycloak-server.war. To start a Keycloak
> instance using rhc you'd use:
>
> # rhc app-create keycloak jbossas-7 --from-code
> https://github.com/keycloak/keycloak-openshift-quickstart.git
>
> We could also make the QuickStart automatically configure Keycloak to use
> PostgreSQL if available. For example if creating a Keycloak instance with
> the following it would use PostgreSQL instead of H2:
>
> # rhc app-create keycloak jbossas-7 postgresql-9.2 --from-code
> https://github.com/keycloak/keycloak-openshift-quickstart.git
>
>
> WildFly
> -------
>
> I've tried to run Keycloak on WildFly and ran into a PicketLink/Hibernate
> issue (see https://issues.jboss.org/browse/KEYCLOAK-135 for details).
> PicketLink guys have merged fix, but that would require upgrading to
> 2.5.3.Final when it's released.
>
> I've also tried to upgrade to PicketLink 2.5.2.Final, but am having some
> issues with the ApplicationData/Entity. When loading the Application from
> the database, PicketLink tries to set a RealmData on
> ApplicationData.resourceUser which you may imagine throws an exception.
> I've added it to https://github.com/stianst/keycloak/tree/pl-2.5. It's
> either a bug in PicketLink, or a mistake in ApplicationData/Entity, I'm
> not sure which though.
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
10:12 a.m.
On 11/1/2013 10:50 AM, Stian Thorgersen wrote:
I've committed something for this now. I added a server war
module, and a dist module. If you build the project with "-Prelease" it will
create a standalone Keycloak server in dist/target. At the moment it is built on-top of AS
7.1.1.Final.
I wish we could distribute EAP.... PM really fucked us by holding up AS7
community releases.
I'd like to also like to have the following:
* remove AS7/Wildfly subsystems that don't make sense to make the distro
smaller.
* Automatically generate keypair/cert for SSL on startup if not already
set up.
* secure JBoss/Wildfly web console with Keycloak. This means adding an
Application to the "Keycloak Adminstration" realm and applying
appropriate permissions to "admin" user.
more comments follow...
Currently the database is not configured and it's just using the
example datasource (H2 in-mem, so data is lost on restart).
----- Original Message -----
> From: "Bill Burke" <bburke(a)redhat.com>
> To: keycloak-dev(a)lists.jboss.org
> Sent: Wednesday, 30 October, 2013 8:08:35 PM
> Subject: Re: [keycloak-dev] Keycloak M1 distribution
>
> I wanted the distro to be AS7 or Wildfly distro, not just a war. All
> preconfigured with SSL, DB, etc. An appliance. Would be cool to
> auto-gen a new key-pair for SSL on initial startup, but not sure how
> feasible that is.
>
> If I had to pick one or the other, distro should take priority over
> Openshift, but we should be able to do both.
An OpenShift QuickStart is really not that much work. We can base it on
https://github.com/stianst/openshift-wildfly, make it dl Keycloak dist instead of WildFly
dist, add some magic around db config. Should be less than a days work.
This will look really nice.
>
> Also, not sure how much it makes sense to ship a Wildfly distro without
> a Wildfly application adapter. I only partially implemented it a few
> months ago. It on the short list for my todo list.
At the moment there's blockers for being able to use WildFly, the adapter and issues
with PicketLink. Besides, it's only a beta at the moment, so I don't think
it's to unreasonable that we ship M1 with AS 7.1.1.Final.
I need to do a Wildfly adapter sooner rather than later to make sure the
Undertow auth model will work with what we want to do. I'm also
currently creating a pure JPA model (see previous email) so we dont'
have to worry about PL issues anymore.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
4074
days inactive
4076
days old
3 comments
2 participants
participants (2)
-
Bill Burke -
Stian Thorgersen