iam.oidc-providers.createRegister an identity provider
Request syntax
POST /iam/api/oidc-providers
{
"url": "string",
"audiences": "array of string"
}Request body
urlRequiredstring
The issuer: a public https:// URL equal to the iss claim of the tokens it signs, e.g. https://token.actions.githubusercontent.com
Constraints: 1-512 chars
audiencesOptionalarray of string
The aud values a token may carry; omitted: the console’s own address, the audience the guides tell a job to request
Constraints: 1-256 chars
Response
201 with the new provider: id, url (normalized), audiences, createdAt, updatedAt and rn, the name a trust policy uses for it.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow iam:CreateOpenIdConnectProvider on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud iam oidc-providers create --url examplecurl -X POST "https://console.platform-development.deutschecloud.app/iam/api/oidc-providers" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"example"}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_iam_oidc-providers_create.