Cloudera · Schema
CreateAbfsCredentialRequest
Request object for creating ABFS cloud credentials. Currently supported cloud credentials: ABFS Access Key for Ambari clusters, ABFS Client Secret for CM clusters.
Big DataData EngineeringData LakehouseData PlatformData WarehouseHadoopHybrid CloudMachine LearningStreaming
Properties
| Name | Type | Description |
|---|---|---|
| name | string | Name of the credential. |
| clusters | array | List of cluster CRNs where the credential should be created. |
| type | object | Type of the credential. Additional required parameters by type: ACCESSKEY: storageAccountName, accessKey; CLIENTKEY: clientId, clientSecretKey, tenantId. Superfluous parameters are ignored. Providing |
| accessKey | string | ABFS access key. |
| storageAccountName | string | ABFS storage account name. |
| clientId | string | Client ID of an Active Directory service principal account. |
| clientSecretKey | string | Client Key of an Active Directory service principal account. |
| tenantId | string | Tenant ID of an Active Directory service principal account. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/cloudera/main/json-schema/cloudera-create-abfs-credential-request-schema.json",
"title": "CreateAbfsCredentialRequest",
"description": "Request object for creating ABFS cloud credentials. Currently supported cloud credentials: ABFS Access Key for Ambari clusters, ABFS Client Secret for CM clusters.",
"x-generated": "2026-10-04",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/cloudera-replicationmanager-api-openapi.yml#/components/schemas/CreateAbfsCredentialRequest",
"type": "object",
"required": [
"name",
"clusters",
"type"
],
"properties": {
"name": {
"description": "Name of the credential.",
"type": "string"
},
"clusters": {
"description": "List of cluster CRNs where the credential should be created.",
"type": "array",
"items": {
"type": "string"
}
},
"type": {
"description": "Type of the credential. Additional required parameters by type: ACCESSKEY: storageAccountName, accessKey; CLIENTKEY: clientId, clientSecretKey, tenantId. Superfluous parameters are ignored. Providing ACCESSKEY will create an ABFS Access Key based account in Ambari. Providing CLIENTKEY will create an Azure Active Directory Service Principal account in Cloudera Manager. ACCESSKEY is only supported on Ambari, while CLIENTKEY is only supported on Cloudera Manager.",
"$ref": "#/$defs/AbfsCloudCredentialType"
},
"accessKey": {
"description": "ABFS access key.",
"type": "string",
"x-sensitive": true
},
"storageAccountName": {
"description": "ABFS storage account name.",
"type": "string"
},
"clientId": {
"description": "Client ID of an Active Directory service principal account.",
"type": "string"
},
"clientSecretKey": {
"description": "Client Key of an Active Directory service principal account.",
"type": "string",
"x-sensitive": true
},
"tenantId": {
"description": "Tenant ID of an Active Directory service principal account.",
"type": "string"
}
},
"$defs": {
"AbfsCloudCredentialType": {
"type": "string",
"description": "ABFS cloud credential type.",
"enum": [
"ACCESSKEY",
"CLIENTKEY"
]
}
}
}
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.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/cloudera-create-abfs-credential-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.