[aerogear-dev] Fwd: [liveoak] Unable to use with iOS push notifications (#270)
matzew at apache.org
Sun Aug 10 08:24:07 EDT 2014
On Sun, Aug 10, 2014 at 2:13 PM, Bruno Oliveira <bruno at abstractj.org> wrote:
> Make passphrase optional defeats the purpose of security. I don't even get
> why those services need a certificate if they skip the bare minimum.
The cert is a thing, required from Apple. Too bad, they can't skip that
> If we are planning to make this happen, ok.
I am not really sure we do that :-)
> But with huge blinking warnings.
Same thought here, add that sentence to the JIRA ;-)
> PGP: 0x84DC9914
> On Sun, Aug 10, 2014 at 5:01 AM, Matthias Wessendorf <matzew at apache.org>
>> I have seen that too, that some services allow no passphrase set. Some
>> even require no passphrase. (i think it was FB/Parse and/or Push.io)
>> If we make passphrase optional, we could help their users tool. At the
>> end, it's users choice to do so, or not.
>> Will create a JIRA for 1.0.0.Final to cover this...
>> ---------- Forwarded message ----------
>> From: *Pauli Jokela* <notifications at github.com>
>> Date: Saturday, August 9, 2014
>> Subject: [liveoak] Unable to use with iOS push notifications (#270)
>> To: liveoak-io/liveoak <liveoak at noreply.github.com>
>> As the current AeroGear implementation does not allow for empty
>> passphrases when adding a push certificate, I'm unable to use the push
>> notification feature at all.
>> A lot of services out there require that a push certificate does NOT have
>> a passphrase set, so it's not an uncommon request.
>> Reply to this email directly or view it on GitHub
>> Sent from Gmail Mobile
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the aerogear-dev