Dependency-Track · Schema

create-workload-identity-provider-request

CompanySBOMSoftware Supply ChainVulnerability ManagementOpen SourceOWASPSecurityCycloneDX

Properties

Name Type Description
name object
type object
issuer string The expected `iss` claim for `OIDC` providers, or the SPIFFE trust domain for `SPIFFE` providers, such as `example.org`.
audience string The value that the token's `aud` claim must contain.
jwks_url string The URL to fetch the signing keys from. Must be `https`.
jwks object An RFC 7517 JSON Web Key Set holding the issuer's public signing keys.
session_lifetime_seconds integer The lifetime of sessions created through this provider, unless a binding sets its own.
View JSON Schema on GitHub

JSON Schema

dependency-track-create-workload-identity-provider-request-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/dependency-track/main/json-schema/dependency-track-create-workload-identity-provider-request-schema.json",
  "title": "create-workload-identity-provider-request",
  "x-generated": "2026-10-09",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/dependency-track-v2-openapi.yml#/components/schemas/create-workload-identity-provider-request",
  "required": [
    "audience",
    "issuer",
    "name",
    "type"
  ],
  "type": "object",
  "properties": {
    "name": {
      "$ref": "#/$defs/workload-identity-provider-name"
    },
    "type": {
      "$ref": "#/$defs/workload-identity-provider-type"
    },
    "issuer": {
      "maxLength": 255,
      "type": "string",
      "description": "The expected `iss` claim for `OIDC` providers, or the SPIFFE trust domain for `SPIFFE` providers, such as `example.org`."
    },
    "audience": {
      "maxLength": 255,
      "type": "string",
      "description": "The value that the token's `aud` claim must contain."
    },
    "jwks_url": {
      "maxLength": 2048,
      "type": "string",
      "description": "The URL to fetch the signing keys from. Must be `https`."
    },
    "jwks": {
      "type": "object",
      "additionalProperties": true,
      "description": "An RFC 7517 JSON Web Key Set holding the issuer's public signing keys."
    },
    "session_lifetime_seconds": {
      "maximum": 86400,
      "minimum": 60,
      "type": "integer",
      "description": "The lifetime of sessions created through this provider, unless a binding sets its own.",
      "format": "int32",
      "default": 3600
    }
  },
  "$defs": {
    "workload-identity-provider-name": {
      "maxLength": 63,
      "pattern": "^[a-zA-Z0-9][a-zA-Z0-9_-]*$",
      "type": "string",
      "description": "The name of the workload identity provider."
    },
    "workload-identity-provider-type": {
      "type": "string",
      "description": "The type of issuer the provider trusts.\n\n* `OIDC`: an OpenID Connect issuer. Tokens must carry an `iss` claim equal to the provider's issuer.\n* `SPIFFE`: a SPIFFE trust domain. The `iss` claim is ignored, and `sub` must be a SPIFFE ID of that trust domain.",
      "enum": [
        "OIDC",
        "SPIFFE"
      ]
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/dependency-track-create-workload-identity-provider-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.