AGSEC-183 UPS user management with Keycloak

Good morning, this is related with the super user Jira. For testing:

user: admin
password: 123 
user: developer
password: developer

Flows to test:

1. Login as admin, create several applications, then logout. Login as developer and check if you can see admin's applications. (they should not be available to developer)
2. Login as developer, create several applications, then logout. Login as admin and check if you can see developer's and admin applications (they should be there)
3. Go to http://localhost:8080/auth/admin/aerogear/console/index.html# and try to login as admin
4. Go to http://localhost:8080/auth/admin/aerogear/console/index.html# and try to login as developer (it should be forbidden)

This pull-request should go into 1.0.x branch and master.
that is an option as well.
Not even create a developer user, up front

On Mon, Oct 13, 2014 at 1:42 PM, Bruno Oliveira <notifications@github.com>
wrote:

> In servers/auth-server/src/main/webapp/WEB-INF/ups-realm.json:
>
> > @@ -28,6 +28,21 @@
> >              "realmRoles": [ "admin" ],
> >              "applicationRoles": {
> >                 "realm-management": [ "realm-admin" ],
> > +               "account": [ "manage-account" ]
> > +            }
> > +        },
> > +        {
> > +            "username" : "developer",
> > +            "enabled": true,
>
> So the user "developer" should be disabled by default, only the role
> "developer" should be available, right?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/aerogear/aerogear-unifiedpush-server/pull/399/files#r18764664>
> .
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf