I disagree.  Users aren't going to download Keycloak and immediately use 
it in production.  Autogenerated self-signed SSL certs, an SMTP server, 
and a preconfigured DB all make sense as then the user can immediately 
use keycloak in development and configure certs, db, etc. later when 
they want to run it in production.

The less things a developer has to do to testdrive keycloak the better. 
 Too bad we can't offer preconfigured social provider.  Then again, I 
guess we could, and hope google, et. al. doesn't shut it down.

On 11/5/2013 10:57 AM, Stian Thorgersen wrote:

Personally I don't think the zip dist should configure smtp, db or ssl. This should be left to an appliance (OpenShift cartridge?) or a hosted solution (keycloak.org?).

* SSL certificates needs to be signed and associated with a domain
* SMTP servers needs to be associated with a domain
* Embedded relational db's are pretty crap and not suitable for production

SMTP has quite a few caveats to make sure emails are not blocked by spam filters.

----- Original Message -----

From: "Bill Burke" <bburke@redhat.com>
To: keycloak-dev@lists.jboss.org
Sent: Tuesday, 5 November, 2013 3:04:45 PM
Subject: [keycloak-dev] bundle an SMTP server?

Along the lines of wanting to run out of the box, is there any reason we
shouldn't bundle an SMTP server (i.e. James) and have it preconfigured?

--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev@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@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev