<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On 05 Nov 2013, at 17:21, Bill Burke <<a href="mailto:bburke@redhat.com">bburke@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">I disagree. Users aren't going to download Keycloak and immediately use<span class="Apple-converted-space"> </span><br>it in production. Autogenerated self-signed SSL certs, an SMTP server,<span class="Apple-converted-space"> </span><br>and a preconfigured DB all make sense as then the user can immediately<span class="Apple-converted-space"> </span><br>use keycloak in development and configure certs, db, etc. later when<span class="Apple-converted-space"> </span><br>they want to run it in production.<br><br>The less things a developer has to do to testdrive keycloak the better.<span class="Apple-converted-space"> </span><br> Too bad we can't offer preconfigured social provider. Then again, I<span class="Apple-converted-space"> </span><br>guess we could, and hope google, et. al. doesn't shut it down.<br></div></blockquote><div><br></div><div>Well… you are *only* risking your google account to be blocked ;) </div><br><blockquote type="cite"><div style="font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br>On 11/5/2013 10:57 AM, Stian Thorgersen wrote:<br><blockquote type="cite">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 (<a href="http://keycloak.org">keycloak.org</a>?).<br><br>* SSL certificates needs to be signed and associated with a domain<br>* SMTP servers needs to be associated with a domain<br>* Embedded relational db's are pretty crap and not suitable for production<br><br>SMTP has quite a few caveats to make sure emails are not blocked by spam filters.<br><br>----- Original Message -----<br><blockquote type="cite">From: "Bill Burke" <<a href="mailto:bburke@redhat.com">bburke@redhat.com</a>><br>To: <a href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>Sent: Tuesday, 5 November, 2013 3:04:45 PM<br>Subject: [keycloak-dev] bundle an SMTP server?<br><br>Along the lines of wanting to run out of the box, is there any reason we<br>shouldn't bundle an SMTP server (i.e. James) and have it preconfigured?<br><br>--<br>Bill Burke<br>JBoss, a division of Red Hat<br><a href="http://bill.burkecentral.com">http://bill.burkecentral.com</a><br>_______________________________________________<br>keycloak-dev mailing list<br>keycloak-dev@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/keycloak-dev<br><br></blockquote></blockquote><br>--<span class="Apple-converted-space"> </span><br>Bill Burke<br>JBoss, a division of Red Hat<br><a href="http://bill.burkecentral.com/">http://bill.burkecentral.com</a><br>_______________________________________________<br>keycloak-dev mailing list<br><a href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a></div></blockquote></div><br></body></html>