Skip to content

Commit

Permalink
Add oidcToken field to pubsub subscription
Browse files Browse the repository at this point in the history
  • Loading branch information
tmshn committed Aug 1, 2019
1 parent bb4c89a commit 909b964
Showing 1 changed file with 24 additions and 0 deletions.
24 changes: 24 additions & 0 deletions products/pubsub/api.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -141,6 +141,30 @@ objects:
- v1beta1: uses the push format defined in the v1beta1 Pub/Sub API.
- v1 or v1beta2: uses the push format defined in the v1 Pub/Sub API.
- !ruby/object:Api::Type::NestedObject
name: oidcToken
description: |
If specified, Pub/Sub will generate and attach an OIDC JWT token as
an Authorization header in the HTTP request for every pushed message.
properties:
- !ruby/object:Api::Type::String
name: serviceAccountEmail
required: true
description: |
Service account email to be used for generating the OIDC token.
The caller (for subscriptions.create, UpdateSubscription, and
subscriptions.modifyPushConfig RPCs) must have the
iam.serviceAccounts.actAs permission for the service account.
- !ruby/object:Api::Type::String
name: audience
description: |
Audience to be used when generating OIDC token. The audience
claim identifies the recipients that the JWT is intended for.
The audience value is a single case-sensitive string. Having
multiple values (array) for the audience field is not supported.
More info about the OIDC JWT token audience here:
https://tools.ietf.org/html/rfc7519#section-4.1.3
Note: if not specified, the Push endpoint URL will be used.
- !ruby/object:Api::Type::Integer
name: 'ackDeadlineSeconds'
description: |
Expand Down

0 comments on commit 909b964

Please sign in to comment.