Connection Methods
Command-Line Arguments
Connect directly on startup by passing connection parameters:
Available CLI Options
| Option | Description |
|---|---|
-H, --host <HOST> | LDAP server hostname |
-p, --port <PORT> | LDAP port (default: 389) |
-D, --bind-dn <DN> | Bind DN for authentication |
-b, --base-dn <DN> | Base DN for browsing |
-c, --config <PATH> | Custom config file path |
CLI arguments override the first connection profile in your config file.
Connection Dialog
Press
F2 at any time to open the connection dialog.From here you can:- Select from saved connection profiles
- Create a new connection
- Edit connection parameters before connecting
Dialog Navigation
| Key | Action |
|---|---|
Tab / Shift+Tab | Move between fields |
e | Enter edit mode (from view mode) |
c | Connect with current settings |
F2 | Cycle TLS mode (edit mode) |
F3 | Cycle credential method (edit mode) |
F10 / Ctrl+Enter | Save profile (edit mode) |
Esc | Cancel and close |
Profiles Layout
Press
F1 to switch to the profiles layout, where you can:- Browse all saved connection profiles
- Organize profiles into folders
- Connect to a profile by pressing
c
j/k) or arrow keys, then press c to connect to the selected profile.See Connection Profiles for detailed information about managing profiles.Connection Parameters
When creating or editing a connection, you’ll configure these fields:Required Fields
- Host
- Port
- Bind DN
- Base DN
The LDAP server hostname or IP address.Examples:
ldap.example.comldap-prod.internal192.168.1.100
Optional Fields
| Field | Default | Description |
|---|---|---|
| TLS Mode | auto | Encryption method (see below) |
| Credential Method | prompt | How to obtain password (see Authentication) |
| Page Size | 500 | Number of entries to fetch per page |
| Timeout | 30 | Connection timeout in seconds |
| Relax Rules | false | Relax LDAP protocol rules for compatibility |
| Read Only | false | Prevent all modifications |
| Folder | (none) | Folder path for organization |
TLS Modes
Loom supports multiple TLS encryption modes:- auto (Recommended)
- ldaps
- starttls
- none
Automatically negotiates the best encryption method:
- Try LDAPS on port 636
- Fall back to StartTLS on port 389
- Fall back to plaintext if both fail
Password Prompts
When a connection usescredential_method = "prompt", you’ll be prompted for the bind password:
- Before TUI starts: If connecting on startup, you’ll see a terminal prompt
- In the TUI: If opening a new connection, a password dialog appears
Skip the Prompt
Set theLOOM_PASSWORD environment variable to provide the password automatically:
Anonymous Bind
To connect anonymously (without authentication), leave the Bind DN field empty:Many LDAP servers restrict what anonymous users can see. You may have limited access to directory entries.
Multiple Connections
Loom supports multiple simultaneous connections through tabs:- Each tab represents an independent LDAP connection
- Press
Ctrl+Rightor typegtto go to the next tab - Press
Ctrl+Leftor typegTto go to the previous tab - Press
Ctrl+Wto close the current tab
Opening Multiple Tabs
- Connect to your first server (any method)
- Press
F2to open the connection dialog again - Select a different profile or enter new connection details
- Connect to create a new tab
Connection Status
The status bar at the bottom shows:- Current connection name or hostname
- Detected server type (OpenLDAP, Active Directory, etc.)
- Key hints for common operations
Troubleshooting
Connection timeout
Connection timeout
If the connection times out:
- Verify the hostname and port are correct
- Check if a firewall is blocking the connection
- Try increasing the
timeout_secsvalue - Test connectivity with:
telnet ldap.example.com 389
TLS/SSL errors
TLS/SSL errors
If you see TLS or certificate errors:
- Try
tls_mode = "none"to test without encryption - Check if the server certificate is valid
- Verify the server supports the TLS mode you’re using
- For self-signed certificates, you may need to accept the certificate (feature support varies by platform)
Bind failed / Invalid credentials
Bind failed / Invalid credentials
If authentication fails:
- Double-check the bind DN format
- Verify the password is correct
- Try connecting with an LDAP tool like
ldapsearchto rule out server issues:
Server type not detected
Server type not detected
If the server type shows as “Unknown”:
- This doesn’t affect functionality
- Some servers don’t expose vendor or version information
- Operations will still work normally
Next Steps
Browsing
Learn how to navigate the directory tree
Authentication
Configure credential methods and password storage
Connection Profiles
Organize and manage saved connections
Searching
Search the directory with LDAP filters