Authentication
#Firebase JWT Auth Policy
Authenticate requests with JWT tokens issued by Firebase. The payload of the JWT
token, if successfully authenticated, with be on the request.user.data
object
accessible to the runtime.
See this document for more information about OAuth authorization in Zuplo.
#Configuration
The configuration shows how to configure the policy in the 'policies.json' document.
{ "name": "my-firebase-jwt-inbound-policy", "policyType": "firebase-jwt-inbound", "handler": { "export": "FirebaseJwtInboundPolicy", "module": "$import(@zuplo/runtime)", "options": { "allowUnauthenticatedRequests": false, "projectId": "my-project-id" } } }json
#Policy Configuration
name
<string>
- The name of your policy instance. This is used as a reference in your routes.policyType
<string>
- The identifier of the policy. This is used by the Zuplo UI. Value should befirebase-jwt-inbound
.handler.export
<string>
- The name of the exported type. Value should beFirebaseJwtInboundPolicy
.handler.module
<string>
- The module containing the policy. Value should be$import(@zuplo/runtime)
.handler.options
<object>
- The options for this policy. See Policy Options below.
#Policy Options
The options for this policy are specified below. All properties are optional unless specifically marked as required.
allowUnauthenticatedRequests
<boolean>
- Allow unauthenticated requests to proceed. This is use useful if you want to use multiple authentication policies or if you want to allow both authenticated and non-authenticated traffic. Defaults tofalse
.projectId
(required)<string>
- Your Firebase Project ID.
#Using the Policy
Read more about how policies work