Creating An JWT Assertion

This page handles the first of the two steps needed to generate an authorized bearer token for use in workflows.

Directions

1. Add a "Create Assertion" action to your workflow.

2. Fill-out the assertion using your information. See the guides and examples below.

Input Fields

Field	Type	What It Is	Example
Service Account Email	String	The email account associated with your service account.	[e-mail]
Scope	String	The scope(s) you are requesting in a space-delimited list. For a full list, see https://developers.google.com/identity/protocols/oauth2/scopes	https://www.googleapis.com/auth/devstorage.read_only https://www.googleapis.com/auth/cloud-platform
Email to Impersonate	String	Email address the service account should perform actions on behalf of; usually a super-admin in your Google organization.	[e-mail]
key	String	They key downloaded from the .PEM file. The same key is reusable.	-----BEGIN PRIVATE KEY----- MIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQDHrpz8eiwwPKev ... O35SvxEYqUvEv9JjXvbeSt73ALUexIpRsZsKJue1eDPicGx1o0iSXoXPjEZfnBvc m3KSBZvEPpg4Z1WlgWYjKgM= -----END PRIVATE KEY-----

For security reasons, you should periodically delete the existing key, generate a new one, and replace it in your Bubble workflow.

Example

In the example below, we are taking the fields from inputs. You can enter your own static text or store the values in the database.