Yep, that sounds good,

the configuration screen can be called out from Menu directly (alongside Account Management and Log out options)?

I guess a submenu (Configuration > Keycloak) or a screen with a link to the Keycloak configuration would be a best fit.

On Wed, Nov 19, 2014 at 11:07 AM, Bruno Oliveira <bruno@abstractj.org> wrote:
Morning my friend, I added a description with some simple rules at
AGPUSH-1111. Quoting here for discussion:

To decouple UPS from Keycloak in separated servers a configuration
interface must be built to generate the appropriate JSON file on the
fly, during the configuration.

Some rules must be respected:

- First time configuration

If the configuration is the first time, just prompt user with the
configuration interface built buy Andres Galante.

- After the URL configuration

If the configuration was already provided and the admin must change it,
he must be logged in to change. Otherwise, change to other Keycloak
server won't be allowed

Does it make any sense for you?


On 2014-11-19, Lukáš Fryč wrote:
> One more question to configuration screen (as I'm not aware it was
> discussed yet),
>
> do we allow users to reconfigure Keycloak instance once it is already in
> use via the configuration screen?
>
> This would be handy if someone installs UPS with defaults and later decides
> to use standalone Keycloak.
>
>
> This would make the things messy /wrt evidence of who created what
> application, but maybe a warning that this information will be lost should
> be okay?
>
>
>
> On Tue, Nov 18, 2014 at 8:55 PM, Bruno Oliveira <bruno@abstractj.org> wrote:
>
> > Help is always welcome. Feel free to create sub-tasks here: AGPUSH-1047
> >
> > Thank you Lukas.
> >
> > On 2014-11-18, Lukáš Fryč wrote:
> > > This seems that makes for pretty good User Experience...
> > >
> > > What about "Built-in" Keycloak instead of Default?
> > > I guess "Keycloak URL" will disappear when "Built-in" is chosen, right?
> > >
> > > Let me know, Brno, if you would appreciate help with prototyping that UI.
> > >
> > >
> > >
> > > On Tue, Nov 18, 2014 at 11:39 AM, Sebastien Blanc <scm.blanc@gmail.com>
> > > wrote:
> > >
> > > >
> > > >
> > > > On Tue, Nov 18, 2014 at 11:34 AM, Bruno Oliveira <bruno@abstractj.org>
> > > > wrote:
> > > >
> > > >> Question: What would be the best for you generate an ups-realm.json
> > file
> > > >> for download based on the current host or let the developer specify
> > the
> > > >> redirect URL?
> > > >>
> > > > I would say, let's use the current host, like we do when we generate
> > the
> > > > code snippets examples.
> > > >
> > > >>
> > > >> I'm thinking about it
> > > >>
> > > >>
> > https://github.com/abstractj/aerogear-unifiedpush-server/commit/db7639566e75f01a8cc79ff18f22daa61cc9cb30#diff-b8df82f22499b0118c37e0e363c4342aR80
> > > >>
> > > >>
> > > >> On 2014-11-17, Matthias Wessendorf wrote:
> > > >> > On Mon, Nov 17, 2014 at 5:17 PM, Matthias Wessendorf <
> > matzew@apache.org
> > > >> >
> > > >> > wrote:
> > > >> >
> > > >> > >
> > > >> > >
> > > >> > > On Mon, Nov 17, 2014 at 5:13 PM, Bruno Oliveira <
> > bruno@abstractj.org>
> > > >> > > wrote:
> > > >> > >
> > > >> > >> Good morning amazing people.
> > > >> > >>
> > > >> > >> While working on AGPUSH-1047, I was wondering if would make
> > sense on
> > > >> > >> having a configuration page before users getting started.
> > > >> > >>
> > > >> > >
> > > >> > > you speak out of my mind, I thought about the same in the train,
> > when
> > > >> I
> > > >> > > saw you changes on GH (the URL replacements to KC and KC.js).
> > > >> > >
> > > >> > > We somehow should have a dialog right after installation, that
> > asks
> > > >> > > "default" or "custom" KC server etc
> > > >> > >
> > > >> >
> > > >> > where
> > > >> > * default would be -> KC and UPS on same server;
> > > >> > custom: Provide URL for KC server
> > > >> >
> > > >> >
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > >>
> > > >> > >> I thinking about the current problem on decoupling our server
> > from
> > > >> > >> Keycloak[1] and OpenShift.
> > > >> > >>
> > > >> > >> What is the current proposal for the initial setup?
> > > >> > >>
> > > >> > >> 1. Developer create an UPS instance on OpenShift
> > > >> > >> 2. Visit https://myups-abstractj.rhcloud.com/ag-push
> > > >> > >> 3. The application automagically redirect to the configuration
> > page
> > > >> with
> > > >> > >> options to skip or enter the URL for the Keycloak server.
> > > >> > >> 4. App changes the keycloak.json/ups-realm.json file based on
> > the URL
> > > >> > >> provided.
> > > >> > >>
> > > >> > >> Does it make sense?
> > > >> > >>
> > > >> > >
> > > >> > > yes, it absolutely does!
> > > >> > >
> > > >> > >
> > > >> > >>
> > > >> > >> [1] -
> > > >> > >>
> > > >>
> > https://github.com/abstractj/aerogear-unifiedpush-server/commit/db7639566e75f01a8cc79ff18f22daa61cc9cb30#diff-f2f2799554171f7ce321785716b71244R3
> > > >> > >>
> > > >> > >> --
> > > >> > >>
> > > >> > >> abstractj
> > > >> > >> PGP: 0x84DC9914
> > > >> > >> _______________________________________________
> > > >> > >> aerogear-dev mailing list
> > > >> > >> aerogear-dev@lists.jboss.org
> > > >> > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >> > >>
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > --
> > > >> > > Matthias Wessendorf
> > > >> > >
> > > >> > > blog: http://matthiaswessendorf.wordpress.com/
> > > >> > > sessions: http://www.slideshare.net/mwessendorf
> > > >> > > twitter: http://twitter.com/mwessendorf
> > > >> > >
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > Matthias Wessendorf
> > > >> >
> > > >> > blog: http://matthiaswessendorf.wordpress.com/
> > > >> > sessions: http://www.slideshare.net/mwessendorf
> > > >> > twitter: http://twitter.com/mwessendorf
> > > >>
> > > >> > _______________________________________________
> > > >> > aerogear-dev mailing list
> > > >> > aerogear-dev@lists.jboss.org
> > > >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >>
> > > >>
> > > >> --
> > > >>
> > > >> abstractj
> > > >> PGP: 0x84DC9914
> > > >> _______________________________________________
> > > >> aerogear-dev mailing list
> > > >> aerogear-dev@lists.jboss.org
> > > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >>
> > > >
> > > >
> > > > _______________________________________________
> > > > aerogear-dev mailing list
> > > > aerogear-dev@lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > >
> >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev@lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev@lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >

> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


--

abstractj
PGP: 0x84DC9914
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev