Good morning, I’ve updated the idea here https://gist.github.com/abstractj/ef1e3d53619796f4e87e Would you like to hear some feedback/questions. Thanks in advance. -- abstractj _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Feel free to post your questions here, sorry about that. My question is: Should the sender implement certificate upload as a feature?

-- abstractj On March 31, 2014 at 2:52:05 PM, Lucas Holmquist (lholmqui(a)redhat.com) wrote: >> wasn't sure where to put the question, so i'll do it here > > > so are you asking if our "sender" clients should also do registration > of apps/variants too? > > well, since the sender clients are just really replacing curl, > then that would probably work

On Monday, March 31, 2014, Bruno Oliveira <bruno@abstractj.org<javascript:_e(%7B%7D,'cvml','bruno@abstractj.org');>> wrote: > Feel free to post your questions here, sorry about that. > > My question is: Should the sender implement certificate upload as a > feature? Nope

> > -- > abstractj > > On March 31, 2014 at 2:52:05 PM, Lucas Holmquist (lholmqui(a)redhat.com) > wrote: > > > wasn't sure where to put the question, so i'll do it here > > > > > > so are you asking if our "sender" clients should also do registration > > of apps/variants too? > > > > well, since the sender clients are just really replacing curl, > > then that would probably work > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Sent from Gmail Mobile

So I think we reached a dead end. If you want passphrase encryption, and they must be reversible because Apple requires it. How your workflow would look like? 1. Login 2. Register an application 3. Make use of our client to encrypt passphrase/certificate 4. Use cURL to upload the encrypted data ???? From the developers perspective I would never use that. If the certificate should be only provided when creating the variant inside Admin UI, you don't need a client like discussed here ( https://issues.jboss.org/browse/AGPUSH-561). Why would I need a client to encrypt files and require cURL to upload it? -- abstractj On March 31, 2014 at 3:16:47 PM, Matthias Wessendorf (matzew@apache.org<javascript:;>) wrote: > > Cä > > On Monday, March 31, 2014( http://airmail.calendar/2014-03-31%2012:00:00%20GMT-3), > Matthias Wessendorf > wrote: > > > > > > On Monday, March 31, 2014( http://airmail.calendar/2014-03-31%2012:00:00%20GMT-3), > Bruno Oliveira > wrote: > > > Feel free to post your questions here, sorry about that. > > > > > > My question is: Should the sender implement certificate upload > as a feature? > > > > Nope > > > The certificate should be only provided when creating the actual > iOS variant (e.g inside the AdminUI - or its REST APIs)

All good, sometimes security and usability never match. That's the reason why I'm asking before. -- abstractj On March 31, 2014 at 4:16:56 PM, Matthias Wessendorf (matzew@apache.org<javascript:;>) wrote: > > Perhaps we never really talked about the same? > > Regarding usability, providing the Apple certificate for every > sending to APNs would be really odd for my point of view ;) > > Anyways, I'd suggest we do a hangout tomorrow to discuss this. > I will share a detailed write-up of our chat. > > Sounds good?