Kemal YAZICI

<p>Has your wordpress website a mobile application? Do you want to push notifications from wordpress website to your application?<br />
Pusher plugin can achieve this job if you use Firebase Cloud Messaging in your application.<br />
If you make the settings in the mobile application correctly, the plugin will push a notification in every new post.</p>
<p>You can find all Firebase Cloud Messaging related information at <a href="https://firebase.google.com/docs/cloud-messaging" rel="nofollow ugc">this address.</a></p>
<h3>How to push notification to mobile app</h3>
<p>You can send a notification to all users who have subscribed to the topic you set from within your application.</p>
<ul>
<li><a href="https://firebase.google.com/docs/cloud-messaging/ios/topic-messaging" rel="nofollow ugc">Send messages to topics on iOS</a></li>
<li><a href="https://firebase.google.com/docs/cloud-messaging/android/topic-messaging" rel="nofollow ugc">Topic messaging on Android</a></li>
</ul>


Pusher – Pushing mobile notification with FCM

If your wordpress site has a mobile application, you can push a notification to the users of your mobile application via this plugin.

Mithun Biswas

<p>If your Firebase client app communicates with a custom backend server, you might need to identify the currently signed-in user on that server.</p>
<p>This plugin work with Google Firebase tokens. You can use it to verify ID Tokens.</p>
<h3>Namespace and Endpoints</h3>
<p>When the plugin is activated, a new namespace is added</p>
<pre><code>/verify-id-tokens/v1/
</code></pre>
<p>Also, a new endpoint is added to this namespace</p>
<p><em>/verify-id-tokens/v1/token/validate</em> | POST</p>
<h3>PHP HTTP Authorization Header enable</h3>
<p>Most of the shared hosting has disabled the <strong>HTTP Authorization Header</strong> by default.</p>
<p>To enable this option you’ll need to edit your <strong>.htaccess</strong> file adding the follow</p>
<pre><code>RewriteEngine on
RewriteCond %{HTTP:Authorization} ^(.*)
RewriteRule ^(.*) - [E=HTTP_AUTHORIZATION:%1]
</code></pre>
<h3>WPENGINE</h3>
<p>To enable this option you’ll need to edit your <strong>.htaccess</strong> file adding the follow</p>
<pre><code>SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
</code></pre>
<h3>Configurate the Firebase projectId</h3>
<p>To add the <strong>projectId</strong> edit your wp-config.php file and add a new constant called <strong>BENGAL_STUDIO_VERIFY_ID_TOKENS_FIREBASE_PROJECT_ID</strong></p>
<pre><code>define('BENGAL_STUDIO_VERIFY_ID_TOKENS_FIREBASE_PROJECT_ID', 'projectId');
</code></pre>
<h3>Configurate CORs</h3>
<p>The <strong>Verify ID Tokens | Firebase</strong> plugin has the option to activate <a href="https://en.wikipedia.org/wiki/Cross-origin_resource_sharing" rel="nofollow ugc">CORs</a> response headers.</p>
<p>To enable the CORs edit your wp-config.php file and add a new constant called <strong>BENGAL_STUDIO_VERIFY_ID_TOKENS_ENABLE_CORS</strong></p>
<pre><code>define('BENGAL_STUDIO_VERIFY_ID_TOKENS_ENABLE_CORS', true);
</code></pre>
<h3>Retrieve ID tokens on clients</h3>
<p>To retrieve the ID token from the client, make sure the user is signed in and then get the ID token from the signed-in user:</p>
<pre><code>firebase.auth().currentUser.getIdToken(/* forceRefresh */ true).then(function(idToken) {
  // Send token to your backend via HTTPS
  // ...
}).catch(function(error) {
  // Handle error
});
</code></pre>
<h3>Verify ID Tokens</h3>
<h4>verify-id-tokens/v1/token/validate</h4>
<p>This is a simple helper endpoint to validate a token; you only will need to make a POST request sending the Authorization header.</p>


Pusher – Pushing mobile notification with FCM vs Verify ID Tokens | Firebase