GMP-JWT generates JWTs suitable for use authenticating to Google Maps Platform APIs.
Supports:
The server (server/main.go) can be customized with the following flags:
| Flag | ENV | |
|---|---|---|
--allowed_apis |
ALLOWED_APIS |
Comma-seperated list of APIs tokens can be generated for, or * for all supported. Defaults to * (all APIs). |
--cors_origins |
CORS_ORIGINS |
Value to set for the 'Access-Control-Allow-Origin' header. Use * for wildcard, which is dangerous in production. |
--enable_appcheck |
ENABLE_APPCHECK |
If set, requests must a valid token from app check in the X-Firebase-AppCheck header. |
--token_duration |
TOKEN_DURATION |
Duration a generated token is valid for (default 30m0s). |
Tokens are generated using an available Service Account via Application Default Credentials.
Practically, this means the either provided automatically when run on Cloud Run, GCE, etc
or manually provided via the GOOGLE_APPLICATION_CREDENTIALS ENV variable.
An apis parameter can be set to pass a list of APIs that the token should include. This list must be a subset of the allowed_apis.
As an example, if the server was started with ALLOWED_APIs=* you could request different tokens using /?apis=routes which will return a
token scoped to the Routes API. /?apis=addressvalidation,routes will return a token scoped to both Address Validation and Routes API.