Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather JD Edwards credentials

Each setup method requires you to pass in credentials generated in JD Edwards. Gather these credentials before you move on.

To set up the JD Edwards connector, you’ll need:

1. The username and password of an account with access to a JD Edwards EnterpriseOne environment configured with an Application Interface Services (AIS) server.

2. The URL of the AIS server.

That’s it! Next, move on to the instructions for your chosen setup method.

Set up a JD Edwards cloud-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of JD Edwards credentials generated by following the instructions above

1. In ConductorOne, click Connectors > Add connector.

2. Search for JD Edwards and click Add.

3. Choose how to set up the new JD Edwards connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. Find the Settings area of the page and click Edit.

7. In the Application Interface Services (AIS) URL field, enter the URL of your AIS server, including the port (https://your_ais_server:port).

8. In the Username and Password fields, enter the credentials for an account with access to the AIS server.

9. Click Save.

10. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your JD Edwards connector is now pulling access data into ConductorOne.

Set up a JD Edwards cloud-hosted connector using Terraform

As an alternative to the cloud-hosted setup process described above, you can use Terraform to configure the integration between JD Edwards and ConductorOne.

See the ConductorOne JD Edwards integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.

Set up a JD Edwards self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of JD Edwards credentials generated by following the instructions above

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the JD Edwards connector

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new JD Edwards connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. Click Rotate to generate a new Client ID and Secret.

   Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your JD Edwards connector deployment:

Secrets configuration

# baton-jd-edwards-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-jd-edwards-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # JD Edwards credentials
  BATON_AIS_URL: <JD Edwards AIS Server URL, including the port (https://your_ais_server:port)>
  BATON_PASSWORD: <JD Edwards EnterpriseOne password>
  BATON_USERNAME: <JD Edwards EnterpriseOne username>

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-jd-edwards.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-jd-edwards
  labels:
    app: baton-jd-edwards
spec:
  selector:
    matchLabels:
      app: baton-jd-edwards
  template:
    metadata:
      labels:
        app: baton-jd-edwards
        baton: true
        baton-app: jd-edwards
    spec:
      containers:
      - name: baton-jd-edwards
        image: ghcr.io/conductorone/baton-jd-edwards:latest
        args: ["service"]
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-jd-edwards-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace baton-jd-edwards
   

2. Apply the secret configuration:

   kubectl -n baton-jd-edwards apply -f baton-jd-edwards-secrets.yaml
   

3. Apply the deployment:

   kubectl -n baton-jd-edwards apply -f baton-jd-edwards.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n c1 get pods
   

2. View the connector logs:

   kubectl -n c1 logs -l app=baton-${baton-jd-edwards}
   

3. Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the JD Edwards connector to. JD Edwards data should be found on the Entitlements and Accounts tabs.

That’s it! Your JD Edwards connector is now pulling access data into ConductorOne.