Quick Start — Basic Auth
Basic auth is the simplest identity posture: a single shared Oracle service account authenticates every backend call. The connectors deploy behind the Context Engine as usual; what “basic” decides is only how the call is attributed to Oracle — as one service account rather than as the named end user.
Prerequisites
Section titled “Prerequisites”- Oracle EPM environment with REST API access
- A service account with appropriate permissions
- Container hosting platform for the connectors and the Context Engine (Azure Container Apps, Docker, etc.)
Step 1: Gather Backend Credentials
Section titled “Step 1: Gather Backend Credentials”For Essbase
Section titled “For Essbase”| Value | Description | Example |
|---|---|---|
| Server URL | Essbase REST API base URL | https://{essbase_host} |
| Username | Service account username | {username} |
| Password | Service account password | — |
For Planning
Section titled “For Planning”| Value | Description | Example |
|---|---|---|
| Server URL | Planning REST API base URL (the connector appends the REST path) | https://{planning_host} |
| Username | Service account username | {username} |
| Password | Service account password | — |
| Identity Domain | Optional, required for some environments | {identity_domain} |
For FCCS
Section titled “For FCCS”| Value | Description | Example |
|---|---|---|
| Server URL | FCCS REST API base URL (the connector appends the REST path) | https://{fccs_host} |
| Username | Service account username | {username} |
| Password | Service account password | — |
| Identity Domain | Optional, required for some environments | {identity_domain} |
Step 2: Deploy the Connector
Section titled “Step 2: Deploy the Connector”See Container Deployment for detailed instructions. Every service-account connector runs with AGENTCUBE_CONNECTOR_MODE=admin.
Recommended: delegated credential (stored in the Context Engine)
Section titled “Recommended: delegated credential (stored in the Context Engine)”The connector environment carries no username or password. You enter the service-account credential in Step 3, when you register the connector.
# EssbaseAGENTCUBE_CONNECTOR_MODE=adminAGENTCUBE_AUTH_MODE=delegated_basicESSBASE_SERVER_URL={essbase_url}
# PlanningAGENTCUBE_CONNECTOR_MODE=adminAGENTCUBE_AUTH_MODE=delegated_basicPLANNING_SERVER_URL={planning_url}
# FCCSAGENTCUBE_CONNECTOR_MODE=adminAGENTCUBE_AUTH_MODE=delegated_basicFCCS_SERVER_URL={fccs_url}A delegated_basic connector refuses to start if {PRODUCT}_USERNAME or {PRODUCT}_PASSWORD is also set; credentials live in one place only. In this mode the connector uses the forwarded username exactly as entered, so for a non-Default Oracle identity domain enter the username in the Context Engine as {identity_domain}.{username}.
Alternative: plain basic (credential on the connector)
Section titled “Alternative: plain basic (credential on the connector)”basic is the connector default, so AGENTCUBE_AUTH_MODE can be omitted.
# EssbaseAGENTCUBE_CONNECTOR_MODE=adminESSBASE_SERVER_URL={essbase_url}ESSBASE_USERNAME={username}ESSBASE_PASSWORD={password}
# PlanningAGENTCUBE_CONNECTOR_MODE=adminPLANNING_SERVER_URL={planning_url}PLANNING_USERNAME={username}PLANNING_PASSWORD={password}# PLANNING_IDENTITY_DOMAIN={identity_domain} # only for non-Default identity domains
# FCCSAGENTCUBE_CONNECTOR_MODE=adminFCCS_SERVER_URL={fccs_url}FCCS_USERNAME={username}FCCS_PASSWORD={password}# FCCS_IDENTITY_DOMAIN={identity_domain} # only for non-Default identity domainsIn basic mode, set PLANNING_USERNAME / FCCS_USERNAME to the bare username; the connector adds the identity-domain prefix itself when PLANNING_IDENTITY_DOMAIN / FCCS_IDENTITY_DOMAIN is set.
AGENTCUBE_CONNECTOR_MODE is required for Planning and FCCS (admin or user, no default) — the connector will not start without it. Essbase accepts admin or user and defaults to user, so a service-account Essbase connector must set admin explicitly: a user-mode connector refuses to start with basic auth. The user (data) connector normally uses SSO (internal), so Oracle sees each person; a delegated credential is an interim alternative. See Single Sign-On.
Step 3: Register with the Context Engine
Section titled “Step 3: Register with the Context Engine”Deploy the Context Engine alongside the connectors and register each connector with it, so the Context Engine can route your AI platform’s calls to the right backend.
- Set
AGENTCUBE_CE_CREDENTIAL_KEYon the Context Engine. It encrypts the credentials and license key the Context Engine stores; without it you cannot register connectors or install a license. See the environment variable reference. - Install your AgentCube license key: sign in to the admin console, open Admin & Security → License, paste the key into License key and select Save. New data sources cannot be added until a valid license is installed.
- Register each connector under Connected Systems. Choose auth mode
delegated_basicand enter the service-account username and password if you used the recommended form in Step 2, ornoneif the credential lives on the connector (basicon the connector itself). The Context Engine’s ownbasicregistration mode also asks for a username and password, which a plain-basic connector ignores, so usenonethere. See Connecting Data Sources for the full registration steps.
See Architecture for the hub model and Connecting to Claude.ai / Connecting to Copilot Studio for the AI-platform side.
Step 4: Connect Your AI Platform
Section titled “Step 4: Connect Your AI Platform”Your AI platform connects to the Context Engine’s single MCP endpoint — not to a connector directly.
Step 5: Verify
Section titled “Step 5: Verify”See Verification to confirm your deployment is working correctly.
Next Steps
Section titled “Next Steps”- Full environment variable reference
- SSO Setup — add a user (data) connector with per-user attribution so Oracle sees the individual user
- Auth Mode Management — the full set of identity postures and the admin-vs-user connector rules