Breadcrumbs

What to Expect

ChatGPT Image Jun 11, 2026, 04_07_09 PM.png

Get ready for onboarding

This page gives you a clear view of the Cantara onboarding journey and the information to gather before your first session. Use it as a preparation checklist so your team can move faster, reduce back-and-forth, and avoid delays.

What to Expect

Here’s the high-level journey. Each step is covered in more detail in the Get Started Guide, but this overview shows what your team is preparing for.

  1. Register your tenant – Create your Cantara account, register your organisation, and select a cloud deployment region.

  2. Manage access control – Choose your authentication method, connect your Identity Provider if required, and set up Security Groups and Security Topics to control what users can access.

  3. Configure namespaces – Create isolated environments, such as development or production, for independent configuration and management within your tenant.

  4. Set up billing and licensing – Configure a billing profile and add licenses to activate your subscription.

  5. Configure gateways – Connect Cantara to your JD Edwards and external systems, and set up gateway-level access control.

What You'll Need Beforehand

1. Tenant Registration

  • Organisation legal name
  • Entity number, such as ACN
  • Business identifier, such as ABN
  • Country
  • Preferred cloud deployment region
  • Tenant display name
  • Tenant system name, noting this is permanent, uses no spaces, and cannot be changed after creation
  • Phone number
  • Support service domain, such as the email domain used for support requests
  • Primary business address
  • Billing address, if different from the primary address
  • Named platform administrator, including name and email

2. Access Control & Identity Provider

  • Authentication method decision: local accounts, SSO, or SSO with SCIM provisioning
  • Identity Provider type, such as Microsoft Entra ID or Okta
  • IdP tenant or directory ID
  • OAuth 2.0 client ID
  • OAuth 2.0 client secret
  • Authorisation endpoint URL
  • Token endpoint URL
  • JWKS URL
  • Redirect URI provided by Cantara during setup
  • ID token claim used for the JDE username, such as email or USERID
  • User groups to assign or sync to Cantara Security Groups
  • Security Topics and permissions required for each group
  • SSO and MFA approval status confirmed with your IAM or security team
  • SCIM provisioning token, if using SCIM
  • IAM or security team contact, including name and email

3. Namespace

  • Namespace name, such as development, test, staging, or production
  • Namespace region

4. Billing & Licensing

  • Billing type, such as annual account billing or monthly credit card billing
  • Billing currency
  • Billing contact name, email, and phone number
  • Credit card details, if using credit card billing
  • License name
  • Required product tiers and entitlements, such as user limits or transaction limits

5. Gateway & JD Edwards Connection

  • Gateway name, which should match the JDE node name
  • Gateway prefix, which must be globally unique and forms part of the gateway URL
  • Time zone where the JDE servers are hosted
  • JDE environment name, such as PY, PD, or DV
  • JDE node name and node password
  • JDE service account username and password
  • JDE role and date format
  • SSL certificate in PKCS#12 format, such as .p12 or .pfx, including the private key
  • Certificate alias, if the keystore contains multiple certificates
  • Certificate file password and key password
  • AIS or JAS endpoint URL, including scheme and host
  • Firewall or IP whitelist rules configured for Cantara IP addresses
  • VPN or private link requirements, if applicable
  • JDE technical contact, including name and email

6. External Systems, If Applicable

  • System name and type, such as CRM, WMS, or another ERP
  • API endpoint URLs and protocol, such as REST or SOAP
  • Authentication method and credentials
  • Expected data flows, including direction, volume, and frequency
  • Rate limits or maintenance windows
  • Technical contact for each system

Tips for a Smoother Start

  • Book the right people early: Include business owners, IAM/security, JDE, networking, and billing contacts.

  • Gather long-lead items first: IdP setup, certificates, firewall/IP allowlisting, VPN/private link requirements, and billing approvals can take time.

  • Use one shared preparation document: Track endpoints, contacts, decisions, and missing items in one place. Store secrets securely rather than in plain text.

  • Start with the highest-value workflow: Choose the first integration or use case you want to prove out during onboarding.

FAQ

What if I don't have all the information yet?

That's okay — you can start onboarding with partial details. We'll flag what's missing and work through it together. Having the core items (contacts, JDE environment, identity provider) will keep things on track.

Does everything need to be finalised before kickoff?

No. The checklist is a guide, not a gate. We can begin planning and discovery while you finalise credentials or approvals in parallel.

Let’s get started

When you are ready to begin, start with Register a Tenant.