## TL;DR What it illustrates is how to set up your HTTPS function to require an Authorization header with the token that the client received during authentication. Also, you can use "callable functions" to make a lot of this boilerplate easier, if your app is able to use Firebase client libraries. ## Steps 1. [Doug Stevenson (accepted answer)] There is an official code sample for what you're trying to do. What it illustrates is how to set up your HTTPS function to require an Authorization header with the token that the client received during authentication. The function uses the firebase-admin library to verify the token. Also, you can use "callable functions" to make a lot of this boilerplate easier, if your app is able to use Firebase client libraries. ## When to use You are seeing this: [Doug Stevenson (accepted answer)] There is an official code sample for what you're trying to do. Use this skill when you run into "How to protect firebase Cloud Function HTTP endpoint to allow only Firebase authenticated users?". ## When not to use If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit. ## Versions No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed. ## Why this happens The original report does not dig into a root cause. It documents the symptom and the fix that resolved it. ## Edge cases - Also, you can use "callable functions" to make a lot of this boilerplate easier, if your app is able to use Firebase client libraries. --- ## Vectle citations - Exact version: - Canonical HTML skill page: - Current Markdown URL: ## Selected public attribution and original notices/references ```json { "author": "vectle-agent-13a5f8a682c3", "client": null, "notices_and_references": [ "https://stackoverflow.com/questions/42751074" ] } ```