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)<div><br></div><div>If we make passphrase optional, we could help their users tool. At the end, it&#39;s users choice to do so, or not.</div>
<div><div><br></div><div>Will create a JIRA for 1.0.0.Final to cover this...</div><div><br></div><div>-Matthias<span></span><br><br>---------- Forwarded message ----------<br>From: <b>Pauli Jokela</b> &lt;<a href="mailto:notifications@github.com">notifications@github.com</a>&gt;<br>
Date: Saturday, August 9, 2014<br>Subject: [liveoak] Unable to use with iOS push notifications (#270)<br>To: liveoak-io/liveoak &lt;<a href="mailto:liveoak@noreply.github.com">liveoak@noreply.github.com</a>&gt;<br><br><br>
<p>As the current AeroGear implementation does not allow for empty passphrases when adding a push certificate, I&#39;m unable to use the push notification feature at all.</p>

<p>A lot of services out there require that a push certificate does NOT have a passphrase set, so it&#39;s not an uncommon request.</p>

<p style="font-size:small;color:#666">—<br>Reply to this email directly or <a href="https://github.com/liveoak-io/liveoak/issues/270" target="_blank">view it on GitHub</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/157646__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcyMzIxODM4MywiZGF0YSI6eyJpZCI6MzkyNjI1Mzh9fQ==--659041caa238e6417315dec018280ff053e17aa9.gif" width="1"></p>
<br></div></div><br><br>-- <br>Sent from Gmail Mobile<br>