Set up an Oracle JD Edwards connector

Capabilities

Resource	Sync	Provision
Accounts
Roles

Gather JD Edwards credentials

Configuring the connector 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:

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

The URL of the AIS server.

Done. Next, move on to the connector configuration instructions.

Configure the JD Edwards connector

To complete this task, you’ll need:

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

Cloud-hosted
Self-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

In C1, navigate to Apps > Connectors and click Add connector.

Search for JD Edwards and click Add.

Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

Find the Settings area of the page and click Edit.

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

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

Click Save.

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

Done. Your JD Edwards connector is now pulling access data into C1.

Follow these instructions to use the JD Edwards connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

Resources

GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new JD Edwards connector

In C1, navigate to Apps > Connectors and click Add connector.

Search for Baton and click Add.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

In the Settings area of the page, click Edit.

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:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 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: public.ecr.aws/conductorone/baton-jd-edwards:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-jd-edwards
        envFrom:
        - secretRef:
            name: baton-jd-edwards-secrets

Step 3: Deploy the connector

Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

Check that the connector data uploaded correctly. In C1, click Apps. 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.

Done. Your JD Edwards connector is now pulling access data into C1.

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up an Oracle JD Edwards connector

Capabilities

Gather JD Edwards credentials

Configure the JD Edwards connector

Resources

Step 1: Set up a new JD Edwards connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Gather JD Edwards credentials

​Configure the JD Edwards connector

​Resources

​Step 1: Set up a new JD Edwards connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather JD Edwards credentials

Configure the JD Edwards connector

Resources

Step 1: Set up a new JD Edwards connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector