JedIN Settings & Configuration — Runtime Profiles, Credentials, Security

Central Configuration for Your Integration Platform

The JedIN Settings page is the control center for your integration environment. Every connection, credential, runtime behavior, and security policy is managed from a single location. Whether you are setting up a new SAP CPI connection, rotating API keys, configuring OAuth tokens, or defining access policies — the Settings page provides a structured interface for all operational configuration.

This guide documents each section of the Settings page based on the production interface, with step-by-step instructions for the most common configuration tasks.

---

Prerequisites

Before configuring settings, confirm you have:

• A JedIN account with Admin or Owner role — most settings require elevated permissions
• External system credentials ready — API keys, OAuth client IDs/secrets, certificates, or basic auth credentials for the systems you plan to connect
• Network access verified — confirm that your JedIN instance can reach the external system endpoints (SAP CPI, SAP C4C, VTEX, databases, etc.)
• Security requirements documented — know your organization's policies for key rotation, certificate management, and access control before configuring

---

Navigating to Settings

1. Log in to JedIN.
2. Click Settings in the left sidebar (gear icon at the bottom of the navigation).
3. The Settings page opens with tabbed sections.

Expected Result: You see the Settings page with tabs for General, Connections, Credentials, Runtime, Security, and Integrations.

---

Section 1: General Settings

The General tab controls your tenant-level configuration.

Tenant Information

• Tenant Name — your organization name displayed across the platform
• Tenant ID — the unique identifier (UUID) used in API calls and multi-tenant isolation
• Tier — your current subscription tier (Free, Starter, Professional, Enterprise) with usage limits displayed

Locale and Display

• Language — select the interface language (pt-BR, en-US, es)
• Timezone — used for scheduling, log timestamps, and monitoring dashboards
• Date Format — ISO-8601 or localized format for display

Expected Result: Changes to general settings apply immediately across the platform for all users in your tenant.

---

Section 2: Connections

Connections define how JedIN reaches external systems. Each connection stores an endpoint URL, authentication method, and optional health-check configuration.

Creating a New Connection

1. Click the Connections tab.
2. Click + New Connection.
3. Fill in the connection form:
   • Name — a descriptive label (e.g., "SAP CPI Production", "VTEX Storefront API")
   • Type — select the connector type from the dropdown (HTTP, OData, JDBC, SFTP, AMQP, Kafka, SAP RFC, etc.)
   • Base URL — the root endpoint (e.g., https://my-tenant.it-cpi018.cfapps.br10.hana.ondemand.com)
   • Authentication — select the method: None, Basic, OAuth 2.0 Client Credentials, OAuth 2.0 Authorization Code, API Key, Certificate (mTLS)
4. Click Test Connection to validate connectivity.
5. Click Save.

Authentication Methods

Method	Fields Required	Use Case
Basic	Username, Password	SAP CPI, legacy systems
OAuth 2.0 Client Credentials	Client ID, Client Secret, Token URL	SAP BTP, Azure AD, AWS
OAuth 2.0 Authorization Code	Client ID, Secret, Auth URL, Token URL, Redirect URI	User-delegated access
API Key	Key Name, Key Value, Location (header/query)	VTEX, HubSpot, third-party APIs
Certificate (mTLS)	Client Certificate (.pem), Private Key (.key), CA Bundle	Banking, government, high-security

Connection Health Checks

Each connection can have an optional health-check endpoint:

• Health Check Path — a lightweight endpoint to verify the system is reachable (e.g., /api/v1/health, /odata/v2/$metadata)
• Interval — how often to check (60s, 300s, 600s)
• Timeout — maximum wait time before marking the connection as unhealthy

Expected Result: Connections with health checks show a green/yellow/red status indicator on the Connections list. Failed connections trigger alerts in the Monitoring dashboard.

---

Section 3: Credentials

Credentials are stored securely and referenced by name in flows and connections. JedIN encrypts all credential values at rest using AES-256 and supports key versioning for rotation.

Managing Credentials

1. Click the Credentials tab.
2. You see a list of all stored credentials with their type, creation date, and last-used timestamp.
3. Click + New Credential to create one.

Credential Types

• Username/Password — basic authentication pairs, stored encrypted
• OAuth Token — client ID + secret pairs with automatic token refresh
• API Key — single key values with optional expiration dates
• Certificate — X.509 certificates with private keys, supports PEM and PKCS#12 formats
• SSH Key — RSA/ED25519 key pairs for SFTP connections
• Custom Secret — arbitrary key-value pairs for custom connectors

Key Rotation

JedIN supports seamless key rotation without downtime:

1. Navigate to an existing credential.
2. Click Rotate.
3. Enter the new credential value.
4. The system creates a new key version while keeping the previous version active for a configurable grace period (default: 24 hours).
5. All flows using this credential automatically pick up the new version on their next execution.

The keyVersion field tracks which version is active. The previous key (ENCRYPTION_KEY_PREVIOUS) remains valid during the grace period, ensuring in-flight executions complete without errors.

Expected Result: After rotation, the credential shows the new version number. The previous version is marked as "deprecated" and auto-expires after the grace period.

---

Section 4: Runtime Profiles

Runtime Profiles define the execution environment for your integration flows — resource limits, scaling behavior, and runtime options.

Default Profile

Every tenant has a default runtime profile that applies to all flows unless overridden:

• CPU Request / Limit — minimum and maximum CPU allocated to each flow execution (e.g., 100m / 500m)
• Memory Request / Limit — minimum and maximum memory (e.g., 128Mi / 512Mi)
• Timeout — maximum execution time before the flow is terminated (default: 300 seconds)
• Retry Policy — number of retries on failure, backoff strategy (fixed, exponential), and delay between retries
• Concurrency — maximum parallel executions per flow (default: 5)

Creating a Custom Profile

1. Click the Runtime tab.
2. Click + New Profile.
3. Configure the resource limits, timeout, retry policy, and concurrency.
4. Give the profile a name (e.g., "High-Memory SAP", "Batch Processing", "Low-Latency API").
5. Click Save.

Assigning Profiles to Flows

In the Flow Designer, open any flow's settings panel and select the runtime profile from the dropdown. The profile takes effect on the next deployment.

Tier Limits

Runtime profiles are constrained by your tier:

Setting	Free	Starter	Professional	Enterprise
Max CPU per flow	250m	500m	2000m	Unlimited
Max Memory per flow	256Mi	512Mi	2Gi	Unlimited
Max Timeout	60s	300s	900s	3600s
Max Concurrency	1	5	20	Unlimited
Custom Profiles	No	1	10	Unlimited

Expected Result: Flows deployed with a custom profile run with the specified resources. Exceeding tier limits shows a validation error when saving the profile.

---

Section 5: Security

The Security section controls access policies, keystores, and audit logging.

Access Policies

Define who can do what across your tenant:

• Roles — Admin, Developer, Viewer, Operator. Each role has predefined permissions.
• Custom Policies — create fine-grained policies (e.g., "Developer can deploy to staging but not production").
• IP Allowlisting — restrict API access to specific IP ranges.

Keystores and Certificates

Manage the certificates used for TLS, mTLS, and message signing:

1. Click Security > Keystores.
2. Upload a keystore (JKS or PKCS#12 format) or individual certificates.
3. Assign the keystore to connections that require it.

Audit Logging

JedIN logs 13 security event types in configurable formats:

• Event Types — login, logout, credential_access, credential_rotate, flow_deploy, flow_execute, settings_change, role_change, connection_create, connection_delete, export, import, api_key_generate
• Formats — JSON (default), CEF (ArcSight), LEEF (QRadar)
• Export — download logs as CSV or forward to your SIEM via webhook

Expected Result: Security events appear in the audit log within seconds. SIEM integration delivers events to your external security platform in the configured format.

---

Section 6: Integration Advisor

The Integration Advisor tab helps you discover and configure new system connections using AI assistance.

1. Click the Integrations tab.
2. Browse available integration templates or describe what you need.
3. The advisor suggests the required connections, credentials, and runtime profiles.
4. Follow the guided setup to configure everything in one flow.

This feature is particularly useful when connecting to complex systems like SAP S/4HANA or Salesforce, where multiple credentials and endpoints may be needed.

Expected Result: The Integration Advisor creates all required connections and credentials in a single guided workflow, reducing setup time from hours to minutes.

---

Common Configuration Scenarios

Scenario: Connect to SAP CPI

1. Create a credential: type OAuth 2.0 Client Credentials, enter Client ID, Secret, and Token URL from your SAP BTP Service Key.
2. Create a connection: type HTTP, base URL = your CPI tenant URL, authentication = the OAuth credential created above.
3. Test the connection.

Scenario: Rotate an Expiring API Key

1. Go to Credentials, find the expiring key.
2. Click Rotate, paste the new key value.
3. All flows continue running with zero downtime.

Scenario: Create a High-Memory Profile for Batch Processing

1. Go to Runtime, create a new profile with 2Gi memory and 900s timeout.
2. Assign it to your batch processing flows.
3. Redeploy the flows.

---

Expected Results

After configuring your settings, you will have:

• Connections to all external systems with validated connectivity and health checks
• Credentials stored securely with encryption at rest and support for rotation
• Runtime profiles tuned to your workload — from lightweight API flows to heavy batch processing
• Security policies enforcing access control, audit logging, and certificate management
• A fully configured integration environment ready for flow development and deployment