Skip to content

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.

  • 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.)
ValueDescriptionExample
Server URLEssbase REST API base URLhttps://{essbase_host}
UsernameService account username{username}
PasswordService account password—
ValueDescriptionExample
Server URLPlanning REST API base URL (the connector appends the REST path)https://{planning_host}
UsernameService account username{username}
PasswordService account password—
Identity DomainOptional, required for some environments{identity_domain}
ValueDescriptionExample
Server URLFCCS REST API base URL (the connector appends the REST path)https://{fccs_host}
UsernameService account username{username}
PasswordService account password—
Identity DomainOptional, required for some environments{identity_domain}

See Container Deployment for detailed instructions. Every service-account connector runs with AGENTCUBE_CONNECTOR_MODE=admin.

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.

# Essbase
AGENTCUBE_CONNECTOR_MODE=admin
AGENTCUBE_AUTH_MODE=delegated_basic
ESSBASE_SERVER_URL={essbase_url}
# Planning
AGENTCUBE_CONNECTOR_MODE=admin
AGENTCUBE_AUTH_MODE=delegated_basic
PLANNING_SERVER_URL={planning_url}
# FCCS
AGENTCUBE_CONNECTOR_MODE=admin
AGENTCUBE_AUTH_MODE=delegated_basic
FCCS_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.

# Essbase
AGENTCUBE_CONNECTOR_MODE=admin
ESSBASE_SERVER_URL={essbase_url}
ESSBASE_USERNAME={username}
ESSBASE_PASSWORD={password}
# Planning
AGENTCUBE_CONNECTOR_MODE=admin
PLANNING_SERVER_URL={planning_url}
PLANNING_USERNAME={username}
PLANNING_PASSWORD={password}
# PLANNING_IDENTITY_DOMAIN={identity_domain} # only for non-Default identity domains
# FCCS
AGENTCUBE_CONNECTOR_MODE=admin
FCCS_SERVER_URL={fccs_url}
FCCS_USERNAME={username}
FCCS_PASSWORD={password}
# FCCS_IDENTITY_DOMAIN={identity_domain} # only for non-Default identity domains

In 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.

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.

  1. Set AGENTCUBE_CE_CREDENTIAL_KEY on 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.
  2. 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.
  3. Register each connector under Connected Systems. Choose auth mode delegated_basic and enter the service-account username and password if you used the recommended form in Step 2, or none if the credential lives on the connector (basic on the connector itself). The Context Engine’s own basic registration mode also asks for a username and password, which a plain-basic connector ignores, so use none there. 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.

Your AI platform connects to the Context Engine’s single MCP endpoint — not to a connector directly.

See Verification to confirm your deployment is working correctly.