Google Binary Authorization
The management interface for Binary Authorization, a service that provides policy-based deployment validation and control for images deployed to Googl (Google OAuth2).
OCNORA ships 10 typed Google Binary Authorization operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google Binary Authorization
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google Binary Authorization
Operations, grouped by what they do to your data.
Create and send 2
Delete and cancel 2
Other operations 1
A sample Google Binary Authorization workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Binary Authorization trigger is needed.
- 2Get Attestorbinary_authorization.get_attestorGets an attestor. Returns NOT_FOUND if the attestor does not exist.
- 3Create Attestorbinary_authorization.create_attestorCreates an attestor, and returns a copy of the new attestor.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 10
- Create AttestorCreates an attestor, and returns a copy of the new attestor.binary_authorization.create_attestor
- Create PolicyCreates a platform policy, and returns a copy of it.binary_authorization.create_policy
- Delete AttestorDeletes an attestor.binary_authorization.delete_attestor
- Delete PolicyDeletes a platform policy.binary_authorization.delete_policy
- Get AttestorGets an attestor. Returns NOT_FOUND if the attestor does not exist.binary_authorization.get_attestor
- Get PolicyGets a platform policy.binary_authorization.get_policy
- List AttestorsLists attestors. Returns INVALID_ARGUMENT if the project does not exist.binary_authorization.list_attestors
- List PoliciesLists platform policies owned by a project in the specified platform. Returns INVALID_ARGUMENT if the project or the platform doesn't exist.binary_authorization.list_policies
- Replace AttestorUpdates an attestor.binary_authorization.replace_attestor
- Validate Attestation OccurrenceReturns whether the given Attestation for the given image URI was signed by the given…binary_authorization.validate_attestation_occurrence
Google Binary Authorization questions
- How does OCNORA authenticate with Google Binary Authorization?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google Binary Authorization?
- 10 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Binary Authorization operation I need is not listed?
- Where Google Binary Authorization has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google Binary Authorization?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Binary Authorization calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google Binary Authorization workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.