Environments | Rinami Knowledge Garden

Overview

An environment in Cantara defines the connection settings, security provider, and credentials used to execute requests against a target JD Edwards (JDE) environment, such as development, test, or production. Use environments to configure how Cantara connects to JDE, including authentication method, access methods, time zone, date format, and AIS/JAS connection details.

Environment-level authentication is separate from Single Sign On (SSO). SSO uses identity providers, such as OAuth 2.0 or SAML, to authenticate interactive users. Environments control how authenticated sessions or direct service calls execute against backend targets, including JDE authentication and API key-based access for service integrations.

Environment security providers and setup guides

Select the appropriate setup guide based on your integration and authentication requirements.

JDE authentication

Use JDE authentication when users or client applications need to establish JDE sessions through Cantara.

Configure JDE credentials, authentication methods, connection endpoints, access methods, and session settings.
For step-by-step setup instructions, see Configure a Cantara Environment for JDE Authentication.

API key authentication

Use API key authentication for direct machine-to-machine, backend service, automated script, or testing integrations that call Cantara endpoints without an interactive user sign-in flow.

Authenticate direct requests using the configured application name and generated API key.
Execute requests under a designated service account and role, with a configurable key lifespan or expiration.
For step-by-step setup instructions, see Configure a Cantara Environment for API Key Authentication.

Best practices

Use dedicated environments for service integrations: When using API keys, create distinct environments for separate applications or services instead of sharing one set of credentials across unrelated integrations.
Scope credentials and roles appropriately: Assign only the required JDE user and role permissions for the environment’s intended purpose.
Plan key lifecycle management: Track API key expiry dates and rotate keys before they expire.