<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 10, 2013 at 2:56 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'd say make STAGING default and enforce developers to upload the<br>
certificate again if she wants to use the same certificate.<br></blockquote><div><br></div><div style>they can't. Apple generates different CERTs for the production/sandbox systems. That's why we have upload for both:</div>
<div style>devCert/devPassPhrase and prodCert/prodPassphrase </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Or maybe an option which says cert-prod.blah - staging/prod. From my<br>
understanding if it defaults to production, we can motivate people to<br>
mistakes in production with a valid certificate. Developers should be<br>
aware of test it before push anything to production.<br></blockquote><div><br></div><div style>So, if both certificates are active, the suggested default would be use the "development" environment, right ?</div>
<div><br></div><div style>I understand that :-) And it's what Rails does as well :) </div><div style><br></div><div style>However, with two active CERTs (prod and dev) I am not sure if it is nice to "require" the inclusion of "staging":"production" inside of the payload, when sending to production.</div>
<div style><br></div><div style>-Matthias</div><div><br></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>
Is just my perspective.<br>
<div class="im"><br>
Matthias Wessendorf wrote:<br>
> BTW.... when creating the iOS varian....<br>
><br>
><br>
> developmentCertificate/Passphrase and productionCertificate/Passphrase<br>
> are the new Formular Values....... (needs to be updated)<br>
><br>
><br>
> -M<br>
><br>
><br>
> On Tue, Jul 9, 2013 at 6:41 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a><br>
</div><div class="im">> <mailto:<a href="mailto:matzew@apache.org">matzew@apache.org</a>>> wrote:<br>
><br>
> Hi,<br>
><br>
> I pushed an early version of it to [1]. It's a branch, not (yet) a PR.<br>
><br>
> Basically here is a how the payloads MIGHT look like:<br>
><br>
> Broadcast Payload:<br>
> {<br>
> "alert":"HELLO!",<br>
> "sound":"default",<br>
> "staging":"development",<br>
> "badge":7,<br>
> "simple-push":"version=123",<br>
> "someKey":"some value",<br>
> "anotherCustomKey":"some other value"<br>
> }<br>
><br>
> Selective Send Payload:<br>
> {<br>
</div>> "alias" : ["<a href="mailto:user@account.com">user@account.com</a> <mailto:<a href="mailto:user@account.com">user@account.com</a>>",<br>
> "<a href="mailto:someone@aerogear.org">someone@aerogear.org</a> <mailto:<a href="mailto:someone@aerogear.org">someone@aerogear.org</a>>", ....],<br>
<div class="im">> "deviceType" : ["iPad", "AndroidTablet"],<br>
> "staging":"development",<br>
> "message": {<br>
> "alert":"HELLO!",<br>
> "sound":"default",<br>
> "badge":7,<br>
> "someKey":"some value",<br>
> "anotherCustomKey":"some other value"<br>
> },<br>
> "simple-push": {<br>
> "SomeCategory":"version=123",<br>
> "anotherCategory":"version=456"<br>
> }<br>
> }<br>
><br>
> Note: if the "staging" is NOT present, the PRODUCTION cert. (if<br>
> present) will be used. If no cert is present ..... a WARNING is<br>
> logged...<br>
><br>
> Also,..... only on iOS....<br>
><br>
><br>
> -Matthias<br>
><br>
> [1]<br>
> <a href="https://github.com/aerogear/aerogear-unified-push-server/tree/ProdCerts" target="_blank">https://github.com/aerogear/aerogear-unified-push-server/tree/ProdCerts</a><br>
><br>
><br>
><br>
><br>
> On Tue, Jul 9, 2013 at 2:40 PM, Matthias Wessendorf<br>
</div><div class="im">> <<a href="mailto:matzew@apache.org">matzew@apache.org</a> <mailto:<a href="mailto:matzew@apache.org">matzew@apache.org</a>>> wrote:<br>
><br>
><br>
><br>
><br>
> On Tue, Jul 9, 2013 at 2:21 PM, Matthias Wessendorf<br>
</div><div class="im">> <<a href="mailto:matzew@apache.org">matzew@apache.org</a> <mailto:<a href="mailto:matzew@apache.org">matzew@apache.org</a>>> wrote:<br>
><br>
><br>
><br>
><br>
> On Tue, Jul 9, 2013 at 2:14 PM, Kris Borchers<br>
</div><div class="im">> <<a href="mailto:kris@redhat.com">kris@redhat.com</a> <mailto:<a href="mailto:kris@redhat.com">kris@redhat.com</a>>> wrote:<br>
><br>
><br>
> On Jul 9, 2013, at 7:09 AM, Matthias Wessendorf<br>
</div><div class="im">> <<a href="mailto:matzew@apache.org">matzew@apache.org</a> <mailto:<a href="mailto:matzew@apache.org">matzew@apache.org</a>>> wrote:<br>
><br>
>><br>
>><br>
>><br>
>> On Tue, Jul 9, 2013 at 2:04 PM, Kris Borchers<br>
</div><div class="im">>> <<a href="mailto:kris@redhat.com">kris@redhat.com</a> <mailto:<a href="mailto:kris@redhat.com">kris@redhat.com</a>>> wrote:<br>
>><br>
>><br>
>> On Jul 9, 2013, at 6:56 AM, Matthias Wessendorf<br>
</div><div class="im">>> <<a href="mailto:matzew@apache.org">matzew@apache.org</a> <mailto:<a href="mailto:matzew@apache.org">matzew@apache.org</a>>> wrote:<br>
>><br>
>>> They could have a "test" variant :) I'd hate to<br>
>>> expose something like "prod/dev" to the sender,<br>
>>> especially since that is ONLY iOS :)<br>
>><br>
>> I guess a test variant would do the job. I'm good<br>
>> either way on that. Probably another thing that<br>
>> would need clear documentation.<br>
>><br>
>><br>
>> I guess having a "staging" : "production" (or<br>
>> "development") is also not a bad thing (helps,<br>
>> perhaps, already for AGPUSH-113.<br>
>><br>
>><br>
>> What would the default be ? My current feeling is that<br>
>> "production" is always used, unless "staging" :<br>
>> "development" is included on the Sender API ?<br>
><br>
> +1 for production default<br>
><br>
><br>
> In that case, no "isProd()" is needed :-)<br>
><br>
><br>
> I mean generally, if both can be "active" (we would just check<br>
> if cert/passphrase is present)<br>
><br>
><br>
><br>
><br>
>><br>
>><br>
>> -Matthias<br>
>><br>
>><br>
>><br>
>>><br>
>>> However, on the long run... you can have a TEST<br>
>>> PushEE server + a "production" one (AGPUSH-113)<br>
>>><br>
>>><br>
>>> On Tue, Jul 9, 2013 at 1:50 PM, Kris Borchers<br>
</div><div class="im">>>> <<a href="mailto:kris@redhat.com">kris@redhat.com</a> <mailto:<a href="mailto:kris@redhat.com">kris@redhat.com</a>>> wrote:<br>
>>><br>
>>><br>
>>> On Jul 9, 2013, at 6:47 AM, Lucas Holmquist<br>
>>> <<a href="mailto:lholmqui@redhat.com">lholmqui@redhat.com</a><br>
</div><div class="im">>>> <mailto:<a href="mailto:lholmqui@redhat.com">lholmqui@redhat.com</a>>> wrote:<br>
>>><br>
>>>> Sounds good.<br>
>>>><br>
>>>> but i wonder if there would be a case where<br>
>>>> both could be active at the same time.<br>
>>>><br>
>>>> for example, some company has an app that<br>
>>>> is in production, now they need to make<br>
>>>> some modifications to it and want to make<br>
>>>> sure that they didn't break their push<br>
>>>> notifications, so they want to send some<br>
>>>> push notifications to the development<br>
>>>> version since they have separate development<br>
>>>> devices.<br>
>>>><br>
>>>> probably an edge case<br>
>>><br>
>>> Hmmm. I'm not sure how edge that is. Seems<br>
>>> like the appropriate development model to be<br>
>>> able to test a change while keeping the<br>
>>> production version running. I think this is a<br>
>>> good case for being able to have both active<br>
>>> and would require the ability to distinguish<br>
>>> between the two in the Sender API.<br>
>>><br>
>>>><br>
>>>><br>
>>>> On Jul 9, 2013, at 7:25 AM, Kris Borchers<br>
</div>>>>> <<a href="mailto:kris@redhat.com">kris@redhat.com</a> <mailto:<a href="mailto:kris@redhat.com">kris@redhat.com</a>>><br>
<div class="im">>>>> wrote:<br>
>>>><br>
>>>>> That all seems sane to me. +1<br>
>>>>><br>
>>>>> On Jul 9, 2013, at 3:57 AM, Matthias<br>
>>>>> Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a><br>
</div><div><div class="h5">>>>>> <mailto:<a href="mailto:matzew@apache.org">matzew@apache.org</a>>> wrote:<br>
>>>>><br>
>>>>>> Hello!<br>
>>>>>><br>
>>>>>> right now the iOS variant does _only_<br>
>>>>>> support upload of an "Development SSL<br>
>>>>>> Certificate" (see [1]). I'd like to add<br>
>>>>>> support for an "Production SSL<br>
>>>>>> Certificate" to the iOS Variant model class.<br>
>>>>>><br>
>>>>>> Besides the second certificate, the model<br>
>>>>>> class _should_ have a field to reflect the<br>
>>>>>> status (is production or not -><br>
>>>>>> isProduction()), so that only one<br>
>>>>>> certificate is ACTIVE. Internally the<br>
>>>>>> "Sender API" would connect against the<br>
>>>>>> differen Apple servers (prod. verus dev),<br>
>>>>>> based on the value of the isProduction()<br>
>>>>>> method.<br>
>>>>>><br>
>>>>>> Exposing "production" (or "development")<br>
>>>>>> on the Sender API would be really ugly.<br>
>>>>>> With the above said, the Sender-API<br>
>>>>>> remains stable.<br>
>>>>>><br>
>>>>>> The value of "isProduction" would be<br>
>>>>>> updateable on the AdminUI (and the<br>
>>>>>> underlying RESTful endpoints).<br>
>>>>>><br>
>>>>>> -Matthias<br>
>>>>>><br>
>>>>>> [1]<br>
>>>>>> <a href="https://github.com/aerogear/aerogear-unified-push-server/blob/master/src/main/java/org/jboss/aerogear/connectivity/model/iOSVariant.java#L38-L41" target="_blank">https://github.com/aerogear/aerogear-unified-push-server/blob/master/src/main/java/org/jboss/aerogear/connectivity/model/iOSVariant.java#L38-L41</a><br>
>>>>>><br>
>>>>>><br>
>>>>>> --<br>
>>>>>> Matthias Wessendorf<br>
>>>>>><br>
>>>>>> blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
>>>>>> sessions:<br>
>>>>>> <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>
</div></div>>>>>>> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>>>>>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>>>>><br>
>>>>> _______________________________________________<br>
>>>>> aerogear-dev mailing list<br>
>>>>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
</div>>>>>> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>>>>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> aerogear-dev mailing list<br>
>>>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
</div>>>>> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>>>> <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>
>>> aerogear-dev mailing list<br>
>>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
</div>>>> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>>> <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>
</div>>>> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>>> <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>
>> aerogear-dev mailing list<br>
>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
</div>>> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>> <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>
</div>>> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">>> <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>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
</div>> <mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>><br>
<div class="im">> <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>
><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>
><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>
><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>
</div><div class="im">> _______________________________________________<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>
</div>abstractj<br>
<div class="HOEnZb"><div class="h5"><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>
</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>