Implement support for sending OIDC auth tokens with request #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds support for OIDC token authentication for HTTP target tasks. Tokens will be issued and signed by the emulator's (insecure) private key. The emulator will accept, and issue tokens for, any ServiceAccountEmail provided by the client.
By default, the JWT
iss
(issuer) field is "http://cloud-tasks-emulator".Optionally, the emulator can host an HTTP OIDC discovery endpoint. This allows your application to verify tokens at runtime with the full online flow.
To enable this, specify an issuer value at startup:
With this flag:
iss
field ofhttp://localhost:8980
http://localhost:8980/.well-known/openid-configuration
http://localhost:8980/jwks
The
-openid-issuer
URL can be anyhttp://hostname:port
value that your application code can route to. The endpoint listens on0.0.0.0
for easy use in docker / k8s environments.You can, of course, export the content of the
/jwks
url if you prefer to hardcode the public keys in your application.