<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Mar 11, 2014 at 12:17 PM, 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">I will start to file Jiras, but answers inline.<br></blockquote><div><br></div><div>great</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
--<br>
abstractj<br>
<div class=""><br>
On March 11, 2014 at 3:17:01 AM, Matthias Wessendorf (<a href="mailto:matzew@apache.org">matzew@apache.org</a>) wrote:<br>
<br>
> ><br>
> > Yes if that makes sense to the others like Android variants. And no if we<br>
> > just want to use it with iOSVariant, into this case that would apply only<br>
> > for iOS applications.<br>
> ><br>
><br>
> Perfect!<br>
><br>
> It does make sense on the 'root' PushApplication. That way other variant<br>
> types can benefit from it as well. I think we can(should?) also encrypt the<br>
> Google API-Key value. And future variants (other networks) will benefit in<br>
> this case as well<br>
<br>
</div>+1<br>
<div><div class="h5">><br>
><br>
> ><br>
> > Currently:<br>
> ><br>
> > curl -3 -v -b cookies.txt -c cookies.txt<br>
> > -i -H "Accept: application/json" -H "Content-type: multipart/form-data"<br>
> > -F "certificate=@/Users/matzew/Desktop/MyProdCert.p12"<br>
> > -F "passphrase=TopSecret"<br>
> > -F "production=true" // make sure you have Production certificate and<br>
> > Provisioning Profile<br>
> ><br>
> > -X POST https://SERVER:PORT<br>
> > /CONTEXT/rest/applications/{pushApplicationID}/iOS<br>
> ><br>
> ><br>
> > Proposed:<br>
> ><br>
> ><br>
> > curl -3 -v -b cookies.txt -c cookies.txt<br>
> > -i -H "Accept: application/json" -H "Content-type: multipart/form-data"<br>
> > -F "certificate=@/Users/matzew/Desktop/encrypted-cert.blah"<br>
> > -F "passphrase=schwarzenegger"<br>
> > -F "production=true" // make sure you have Production certificate and<br>
> > Provisioning Profile<br>
> ><br>
> > -X POST https://SERVER:PORT<br>
> > /CONTEXT/rest/applications/{pushApplicationID}/iOS<br>
> ><br>
> > Where encrypted-cert.blah and "Schwarzenegger" are encrypted data.<br>
> ><br>
><br>
> Ok, so the encrypted data is being uploaded by the user of the UPS, right ?<br>
> and hence, no more a direct upload of the plain certificate and the plain<br>
> passphrase.<br>
> That means there is an extra step for the user, if I see it correct.<br>
><br>
> having an extra step for the API to create the (iOS) variant is fine, let's<br>
> make sure it's a somewhat simple step for our users, which hopefully than<br>
> does not need too much extra steps in the documentation :-)<br>
<br>
</div></div>I will think about how to make it less painful to our devs<br></blockquote><div><br></div><div><br></div><div>awesome! </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
><br>
><br>
><br>
> > Makes sense?<br>
> ><br>
><br>
> Yes, I think :-)<br>
> Thanks!<br>
><br>
> -Matthias<br>
><br>
><br>
> ><br>
> > ><br>
> > ><br>
> > > ><br>
> > > > Does it make sense to you?<br>
> > > ><br>
> > ><br>
> > > Somewhat - not sure I fully understood :)<br>
> > ><br>
> > ><br>
> > > ><br>
> > > > --<br>
> > > > abstractj<br>
> > > ><br>
> > > > JBoss, a division of Red Hat<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>
> > ><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>
> > > 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>
</div></div></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>