Gateways

Overview

A Gateway provides secure connectivity between Cantara and JD Edwards (JDE) systems.

Gateways are created within a namespace and act as the routing and access-control layer between Cantara and JDE. Authenticated requests from Cantara are processed through a Gateway before reaching JDE services or functions.

In addition to existing JDE security, Gateways provide service and function-level access control using JDE roles or Identity Provider (IdP) groups.

Gateways can also support multiple environments, integrations, or middleware scenarios.

Key functions of a Gateway include:

• Routing authenticated requests from Cantara to JDE

• Enforcing secure communication using certificates

• Controlling access to services and functions based on JDE roles or Identity Provider (IdP) groups

• Supporting multiple gateways to allow context-aware access and middleware scenarios

Key capabilities

Gateways support:

• Secure routing of authenticated requests to JDE

• Certificate-based communication

• Access control using JDE roles or IdP groups

• Service and function-level permission control

• Multiple gateway configurations for different environments or integrations

Key points

• A Gateway must belong to a namespace

• Certificates are required for secure communication

• Gateway access control supplements existing JDE permissions

• Users must still have appropriate JDE access

• Multiple Gateways can be configured within a tenant

Best Practices

• Use descriptive names for gateways to clearly indicate the environment or system it connects to.

• Limit access to only required services to reduce security risks.

• Maintain secure storage of certificates and signing keys.

• Document gateway configurations to support auditing and troubleshooting.