Package Information
Documentation
n8n-nodes-ome-auth
This is an n8n community node. It lets you use Dell OpenManage Enterprise (OME) authentication in your n8n workflows.
Dell OpenManage Enterprise is a centralized systems management solution that provides monitoring, configuration, and lifecycle management for Dell infrastructure via a REST API. This node creates an OME API session and returns an X-Auth-Token that can be used in subsequent API calls.
n8n is a fair-code licensed workflow automation platform.
Installation
Operations
Credentials
Compatibility
Usage
Resources
Version history
Installation
Follow the official installation guide in the n8n community nodes documentation.
Or install manually inside your n8n custom nodes directory:
npm install @arwinho/n8n-nodes-ome-auth
Restart n8n after installation.
Operations
OME Auth
Login
Creates an authenticated session with Dell OpenManage Enterprise using:
POST /api/SessionService/Sessions
The node:
- Authenticates using stored credentials
- Extracts the
X-Auth-Tokenfrom the response - Returns the token for use in downstream nodes
- Optionally skips SSL certificate validation (for self-signed or expired certificates)
Credentials
Create credentials of type:
Dell OpenManage Enterprise API
Prerequisites
- A reachable Dell OpenManage Enterprise instance
- API access enabled
- A valid OME user account with permission to create API sessions
Credential fields
| Field | Description |
|---|---|
| Base URL | Base URL of your OME instance (for example https://ome.example.local) |
| Username | OME username |
| Password | OME password |
| Allow Insecure TLS | Disable SSL certificate validation (for self-signed or expired certificates) |
TLS Behavior
If your OME appliance uses:
- Self-signed certificates
- Expired certificates
- Internal CA certificates
Enable Allow Insecure TLS.
⚠️ Only enable this option in trusted environments. Disabling SSL validation reduces connection security.
Compatibility
- Minimum n8n version: 1.0.0
- Tested against: n8n v1.x and v2.x
- Compatible with Dell OpenManage Enterprise REST API (
SessionServiceendpoint)
If you experience TLS-related issues, ensure your OME certificate is valid or enable the "Allow Insecure TLS" option.
Usage
Step 1 — Add the OME Auth Node
Add OME Auth at the start of your workflow and configure it with your OME credentials.
Step 2 — Use the Token in HTTP Request Nodes
The node outputs an item similar to:
{
"xAuthToken": "your-token",
"headers": {
"X-Auth-Token": "your-token"
},
"setCookie": []
}
In downstream HTTP Request nodes, add a header:
- Name:
X-Auth-Token - Value:
{{$json.headers["X-Auth-Token"]}}
If referencing the auth node explicitly:
{{$node["OME Auth"].json.headers["X-Auth-Token"]}}
You can now call any OME API endpoint.
Example Workflow
OME Auth → HTTP Request (GET /api/DeviceService/Devices)
Header:
X-Auth-Token: {{$node["OME Auth"].json.headers["X-Auth-Token"]}}