[aerogear-dev] Exposing UPS Variants through the endpoints for application use

[Matthias Wessendorf]

Hello Matt,


On Fri, Mar 21, 2014 at 10:40 PM, Matt Wringe <mwringe at redhat.com> wrote:

> I am trying to set up some integration in LiveOak with UPS so that
> LiveOak can send out push notifications.
>
> Currently I have the application's UPS configuration options stored in
> LiveOak (ie variant id, secret, gcm number, UPS url, etc) and the
> application fetches the options from there so that it can do the UPS
> registration. This is so we can manage the variants on the LiveOak side
> and not have to have them hard coded in a native application itself.
>
> Ideally, instead of us storing the variant options in LiveOak, it would
> be great if we could use the UPS endpoints to fetch the variant data
> directly. We could do this now using the endpoints and the admin
> account,


yes - the account for the "push admin" would be the one to use - for now



> but wondering if there is any option (or any planned option) to
> support having more read-only accounts to fetch this kind of data?
> Something like oauth scopes might would work really well here.
>

that's an interesting request. On a branch we started working on keycloak
integration,
so once that is complete, I guess it would be that kinda of place to add
support for your request



>
> Thanks,
>
> Matt Wringe
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140321/85820fb9/attachment-0001.html