<div dir="ltr">Yep, that sounds good,<div><br></div><div>the configuration screen can be called out from Menu directly (alongside Account Management and Log out options)?</div><div><br></div><div>I guess a submenu (Configuration > Keycloak) or a screen with a link to the Keycloak configuration would be a best fit.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 19, 2014 at 11:07 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">Morning my friend, I added a description with some simple rules at<br>
AGPUSH-1111. Quoting here for discussion:<br>
<br>
To decouple UPS from Keycloak in separated servers a configuration<br>
interface must be built to generate the appropriate JSON file on the<br>
fly, during the configuration.<br>
<br>
Some rules must be respected:<br>
<br>
- First time configuration<br>
<br>
If the configuration is the first time, just prompt user with the<br>
configuration interface built buy Andres Galante.<br>
<br>
- After the URL configuration<br>
<br>
If the configuration was already provided and the admin must change it,<br>
he must be logged in to change. Otherwise, change to other Keycloak<br>
server won't be allowed<br>
<br>
Does it make any sense for you?<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
On 2014-11-19, Lukáš Fryč wrote:<br>
> One more question to configuration screen (as I'm not aware it was<br>
> discussed yet),<br>
><br>
> do we allow users to reconfigure Keycloak instance once it is already in<br>
> use via the configuration screen?<br>
><br>
> This would be handy if someone installs UPS with defaults and later decides<br>
> to use standalone Keycloak.<br>
><br>
><br>
> This would make the things messy /wrt evidence of who created what<br>
> application, but maybe a warning that this information will be lost should<br>
> be okay?<br>
><br>
><br>
><br>
> On Tue, Nov 18, 2014 at 8:55 PM, Bruno Oliveira <<a href="mailto:bruno@abstractj.org">bruno@abstractj.org</a>> wrote:<br>
><br>
> > Help is always welcome. Feel free to create sub-tasks here: AGPUSH-1047<br>
> ><br>
> > Thank you Lukas.<br>
> ><br>
> > On 2014-11-18, Lukáš Fryč wrote:<br>
> > > This seems that makes for pretty good User Experience...<br>
> > ><br>
> > > What about "Built-in" Keycloak instead of Default?<br>
> > > I guess "Keycloak URL" will disappear when "Built-in" is chosen, right?<br>
> > ><br>
> > > Let me know, Brno, if you would appreciate help with prototyping that UI.<br>
> > ><br>
> > ><br>
> > ><br>
> > > On Tue, Nov 18, 2014 at 11:39 AM, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>><br>
> > > wrote:<br>
> > ><br>
> > > ><br>
> > > ><br>
> > > > On Tue, Nov 18, 2014 at 11:34 AM, Bruno Oliveira <<a href="mailto:bruno@abstractj.org">bruno@abstractj.org</a>><br>
> > > > wrote:<br>
> > > ><br>
> > > >> Question: What would be the best for you generate an ups-realm.json<br>
> > file<br>
> > > >> for download based on the current host or let the developer specify<br>
> > the<br>
> > > >> redirect URL?<br>
> > > >><br>
> > > > I would say, let's use the current host, like we do when we generate<br>
> > the<br>
> > > > code snippets examples.<br>
> > > ><br>
> > > >><br>
> > > >> I'm thinking about it<br>
> > > >><br>
> > > >><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>
> > > >><br>
> > > >><br>
> > > >> On 2014-11-17, Matthias Wessendorf wrote:<br>
> > > >> > On Mon, Nov 17, 2014 at 5:17 PM, Matthias Wessendorf <<br>
> > <a href="mailto:matzew@apache.org">matzew@apache.org</a><br>
> > > >> ><br>
> > > >> > wrote:<br>
> > > >> ><br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > > On Mon, Nov 17, 2014 at 5:13 PM, Bruno Oliveira <<br>
> > <a href="mailto:bruno@abstractj.org">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<br>
> > 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,<br>
> > when<br>
> > > >> 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<br>
> > 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<br>
> > 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<br>
> > page<br>
> > > >> 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<br>
> > the URL<br>
> > > >> > >> provided.<br>
> > > >> > >><br>
> > > >> > >> Does it make sense?<br>
> > > >> > >><br>
> > > >> > ><br>
> > > >> > > yes, it absolutely does!<br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > >><br>
> > > >> > >> [1] -<br>
> > > >> > >><br>
> > > >><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">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">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">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>
> > > > 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>
> > > ><br>
> ><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>
> ><br>
> ><br>
> > --<br>
> ><br>
> > abstractj<br>
> > PGP: 0x84DC9914<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>
> ><br>
<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>
<br>
<br>
--<br>
<br>
abstractj<br>
PGP: 0x84DC9914<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></div></div></blockquote></div><br></div>