<div dir="ltr">Hello Matt,<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Mar 21, 2014 at 10:40 PM, Matt Wringe <span dir="ltr"><<a href="mailto:mwringe@redhat.com" target="_blank">mwringe@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I am trying to set up some integration in LiveOak with UPS so that<br>
LiveOak can send out push notifications.<br>
<br>
Currently I have the application's UPS configuration options stored in<br>
LiveOak (ie variant id, secret, gcm number, UPS url, etc) and the<br>
application fetches the options from there so that it can do the UPS<br>
registration. This is so we can manage the variants on the LiveOak side<br>
and not have to have them hard coded in a native application itself.<br>
<br>
Ideally, instead of us storing the variant options in LiveOak, it would<br>
be great if we could use the UPS endpoints to fetch the variant data<br>
directly. We could do this now using the endpoints and the admin<br>
account,</blockquote><div><br></div><div>yes - the account for the "push admin" would be the one to use - for now</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
but wondering if there is any option (or any planned option) to<br>
support having more read-only accounts to fetch this kind of data?<br>
Something like oauth scopes might would work really well here.<br></blockquote><div><br></div><div>that's an interesting request. On a branch we started working on keycloak integration,</div><div>so once that is complete, I guess it would be that kinda of place to add support for your request</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks,<br>
<br>
Matt Wringe<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><br clear="all"><div><br></div>-- <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>
</div></div>