Breadcrumbs

Introduction to Gateways

Overview

Once a namespace has been created, the next step is to configure a gateway.

A Gateway provides controlled and secure access between the Cantara Administration Console and JD Edwards (JDE). It acts as the connection point through which authenticated requests are routed from Cantara to JDE.

A gateway must be created within a namespace, and it cannot exist independently of a namespace.

Authentication is handled through an external Identity Provider (IdP), and secure communication is supported using certificates for request signing and transport security.

A Gateway ensures that only authorised requests reach JDE systems.

The Gateway also provides additional access control capabilities, allowing service and function-level access to be restricted based on JDE roles or Identity Provider (IdP) groups.

What Does a Gateway Do?

  • Request Routing — Authenticated requests are routed from Cantara to JD Edwards through the gateway.

  • Authentication — Authentication is handled through an external Identity Provider (IdP), and secure communication is supported using certificates for request signing and transport security.

  • Access Control — The gateway provides additional access control capabilities, allowing service and function-level access to be restricted based on JDE roles or Identity Provider (IdP) groups.

CIP7 Banner - Landscape (1).png

Explore This Section

mermaid-diagram (3).png

How Gateways Fit into the Architecture

Cantara follows a hierarchical structure:

  • Tenant — Your top-level environment in Cantara.

  • Namespace — Sits within a tenant and isolates configuration for a specific purpose (e.g., a development or production environment).

  • Gateway — Created within a namespace and handles the connection to your JD Edwards environment.


What's next?

For instructions on setting up your first gateway, see Configuring Your First Gateway.