<div dir="ltr">This seems that makes for pretty good User Experience...<div><br></div><div>What about "Built-in" Keycloak instead of Default?</div><div>I guess "Keycloak URL" will disappear when "Built-in" is chosen, right?</div><div><br></div><div>Let me know, Brno, if you would appreciate help with prototyping that UI.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 18, 2014 at 11:39 AM, Sebastien Blanc <span dir="ltr"><<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Tue, Nov 18, 2014 at 11:34 AM, Bruno Oliveira <span dir="ltr"><<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Question: What would be the best for you generate an ups-realm.json file<br>
for download based on the current host or let the developer specify the<br>
redirect URL?<br></blockquote></span><div>I would say, let's use the current host, like we do when we generate the code snippets examples. </div><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I'm thinking about it<br>
<a href="https://github.com/abstractj/aerogear-unifiedpush-server/commit/db7639566e75f01a8cc79ff18f22daa61cc9cb30#diff-b8df82f22499b0118c37e0e363c4342aR80" target="_blank">https://github.com/abstractj/aerogear-unifiedpush-server/commit/db7639566e75f01a8cc79ff18f22daa61cc9cb30#diff-b8df82f22499b0118c37e0e363c4342aR80</a><br>
<div><div><br>
<br>
On 2014-11-17, Matthias Wessendorf wrote:<br>
> On Mon, Nov 17, 2014 at 5:17 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>><br>
> wrote:<br>
><br>
> ><br>
> ><br>
> > On Mon, Nov 17, 2014 at 5:13 PM, Bruno Oliveira <<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>><br>
> > wrote:<br>
> ><br>
> >> Good morning amazing people.<br>
> >><br>
> >> While working on AGPUSH-1047, I was wondering if would make sense on<br>
> >> having a configuration page before users getting started.<br>
> >><br>
> ><br>
> > you speak out of my mind, I thought about the same in the train, when I<br>
> > saw you changes on GH (the URL replacements to KC and KC.js).<br>
> ><br>
> > We somehow should have a dialog right after installation, that asks<br>
> > "default" or "custom" KC server etc<br>
> ><br>
><br>
> where<br>
> * default would be -> KC and UPS on same server;<br>
> custom: Provide URL for KC server<br>
><br>
><br>
> ><br>
> ><br>
> ><br>
> ><br>
> >><br>
> >> I thinking about the current problem on decoupling our server from<br>
> >> Keycloak[1] and OpenShift.<br>
> >><br>
> >> What is the current proposal for the initial setup?<br>
> >><br>
> >> 1. Developer create an UPS instance on OpenShift<br>
> >> 2. Visit <a href="https://myups-abstractj.rhcloud.com/ag-push" target="_blank">https://myups-abstractj.rhcloud.com/ag-push</a><br>
> >> 3. The application automagically redirect to the configuration page with<br>
> >> options to skip or enter the URL for the Keycloak server.<br>
> >> 4. App changes the keycloak.json/ups-realm.json file based on the URL<br>
> >> provided.<br>
> >><br>
> >> Does it make sense?<br>
> >><br>
> ><br>
> > yes, it absolutely does!<br>
> ><br>
> ><br>
> >><br>
> >> [1] -<br>
> >> <a href="https://github.com/abstractj/aerogear-unifiedpush-server/commit/db7639566e75f01a8cc79ff18f22daa61cc9cb30#diff-f2f2799554171f7ce321785716b71244R3" target="_blank">https://github.com/abstractj/aerogear-unifiedpush-server/commit/db7639566e75f01a8cc79ff18f22daa61cc9cb30#diff-f2f2799554171f7ce321785716b71244R3</a><br>
> >><br>
> >> --<br>
> >><br>
> >> abstractj<br>
> >> PGP: 0x84DC9914<br>
> >> _______________________________________________<br>
> >> aerogear-dev mailing list<br>
> >> <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
> >> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
> >><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > Matthias Wessendorf<br>
> ><br>
> > blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
> > sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
> > twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><br>
> ><br>
><br>
><br>
><br>
> --<br>
> Matthias Wessendorf<br>
><br>
> blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
> sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
> twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><br>
<br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
--<br>
<br>
abstractj<br>
PGP: 0x84DC9914<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div></div></div><br></div></div>
<br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div>