At this point reading through the docs from Firebase, and the fact that Broadcom didn't seem to update the Gateway to the newer version there really aren't alot of options open to you.
If you are on the virtual appliance your options are really limited. With a software gateway you could install their SDK and do this through the Javascript policy portion and probably get this to work.
All of their code samples seem to be steering toward either an app integrated solution or node.js implementation, in other words build your own software API Gateway on node.js. I wouldn't recommend trying to do this on the API Gateway itself as I'm not sure there would be a "clean" way to get it to run without impact the gateway in some fasion. I would recommend doing the Node.js path just from their docs it seems the easiest to implement and quickest to get up and running.
I would also recommend opening a ticket with Firebase as see if they've had any other tickets or complaints around this change that have facilitated them maybe coming up with some internal docs for options. I would also recommend opening a ticket with Brodcom, this way you can turn it into an enhancement request and it seems like this might impact other companies that they would be working it into their roadmap or as an Integration kit.
Original Message:
Sent: Oct 11, 2024 04:44 PM
From: spalepu
Subject: Legacy Firebase HTTP Interface for Push Notifications to be retired in June 2024
Hi Greg,
I wanted to check with you on the possible solution for new firebase cloud messaging api ?
I am currently trying to implement the authorization solution defined in the documentation https://firebase.google.com/docs/cloud-messaging/migrate-v1#node.js_1 .
Please let me know if we got a solution provided by Broadcom.
Thanks,
Swathi
Original Message:
Sent: Jul 26, 2023 09:22 AM
From: Gregory Thompson
Subject: Legacy Firebase HTTP Interface for Push Notifications to be retired in June 2024
Hi David,
We are looking to make the updates for this for our upcoming SDK 2.4 release (tentatively planned for November). The engineering team would like to meet with you if possible to discuss the solution and get your feedback. If you are able to do this, please reach out to me directly at gregory.thompson@broadcom.com.
Thanks,
------------------------------
Greg Thompson
Layer7 Product Management
Original Message:
Sent: Jul 17, 2023 05:36 AM
From: David Vinell
Subject: Legacy Firebase HTTP Interface for Push Notifications to be retired in June 2024
Hi,
MAG Version is 4.2.1.2809
SDK is a mix of 2.2 / 2.3 ... it will all be 2.3 in a couple of months.
Regards,
Dave V.
Original Message:
Sent: Jul 13, 2023 01:17 PM
From: Gregory Thompson
Subject: Legacy Firebase HTTP Interface for Push Notifications to be retired in June 2024
Hi David,
Can you confirm which version of the MAG and SDK you are currently using? We are looking into this but do not have a final answer at this point.
------------------------------
Greg Thompson
Layer7 Product Management
Original Message:
Sent: Jun 29, 2023 05:06 AM
From: David Vinell
Subject: Legacy Firebase HTTP Interface for Push Notifications to be retired in June 2024
Hi,
We recently received notification from Google that the legacy HTTP Firebase Interface for sending push notifications is going to retired next year.
We are currently using this interface as suggested in the MAG documentation, and it works well for us.
Should we make plans to develop our own alternative to this, or will Broadcom supply something (e.g. an additional assertion built using the Firebase SDK) before June 2024?
Best Regards,
Dave V.
-------------------------------------------------
Hi,
We're writing to let you know that starting June 20, 2024 the legacy Firebase Cloud Messaging (FCM) APIs will be discontinued.
What do you need to know?
On June 20, 2024, we're reducing the number of Firebase Cloud Messaging (FCM) legacy register APIs and legacy send APIs that provide similar functionality. This step will allow us to provide you with a more consistent experience and align with Google security standards to improve security, reliability and performance.
Because of these API decommissions, some already-deprecated SDKs and features will stop working after June 20, 2024.
Please consult the tables below to find which Firebase Cloud Messaging (FCM) APIs and corresponding services/SDKs/features will be discontinued and replaced with new alternatives.
Legacy HTTP Protocol | Sending messages via the Legacy HTTP API. | Send messages via the HTTP v1 API. |