Firebase Cloud Messaging no longer has a server key implementation

[alucard835]

The API Key section in this tutorial is no longer applicable to Firebase Cloud Messaging. Google has changed how their Cloud Messaging services is consumed, and it's no longer a single server API key. It's unclear where an API Key should be generated in Firebase in order to link to Notifications Hubs now.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 2045c90e-edae-77ba-d115-366e72c4326f
• Version Independent ID: 172fdb07-e39d-3d8b-ed64-6a88c8cbf8a2
• Content: Set up push notifications in Azure Notification Hubs
• Content Source: articles/notification-hubs/configure-notification-hub-portal-pns-settings.md
• Service: notification-hubs
• GitHub Login: @sethmanheim
• Microsoft Alias: sethm

[Grace-MacJones-MSFT]

thanks for bringing this to our attention. I have assigned the issue to the content author to evaluate and update as appropriate

[angularsen]

Update:
Cross-posted to #93552 (comment)

@Grace-MacJones-MSFT
Firebase just announced FCM server key authentication will stop working June 21, 2024.
I assume this will require Notification Hubs to support oauth2 to generate short-lived access tokens instead.

I don't know where to report this to the Notification Hubs team, but please forward this to the relevant team and post back a link to an issue or somewhere we can monitor progress on this feature as many will need to re-configure their Notification Hubs in the next year.

https://firebase.google.com/support/faq#fcm-23-deprecation

I believe this is the relevant change:

Device management API	https://fcm.googleapis.com/fcm/notification	The endpoint will continue to work but it won’t support authentication using static server keys after 6/21/2024.	Use an OAuth 2.0 access token derived from a service account.

This is how the same change was described in the email notification:

Discontinued Feature	Decommissioned service	New alternative
Server keys	Authenticating requests with server keys.	Authenticate requests with access tokens generated from authorized service accounts

[nicop85]

Are there any news about this deadline @angularsen pointed out? Someone should start looking for a solution to this problem

[nampham30698]

Any update on this?

[SylberG]

Are there any news about this deadline @angularsen pointed out? Someone should start looking for a solution to this problem

Any update on this?

I think this may answer your question: https://learn.microsoft.com/en-us/azure/notification-hubs/notification-hubs-gcm-to-fcm#current-state

[angularsen]

So basically there is a time window from March 1 until June 30 to complete a rather significant migration, to change client devices to register with FCM instead of legacy, remove the legacy registrations to avoid duplicates and then update the server to use FCM API.

That's not a whole lot of time for absolutely everyone to jump when they say so, but at least there is a heads up now to prepare some of the migration steps.

[sethmanheim]

Please see the updated GCM to FCM migration steps: https://learn.microsoft.com/en-us/azure/notification-hubs/notification-hubs-gcm-to-fcm.

As we are moving to a new feedback system, please reopen this issue or contact Microsoft Support if you still want to provide feedback on the documentation. Thank you! #please-close