Openlink License Manager

OpenLink License Manager Skill

Purpose

Manage the OpenLink License Manager daemon (oplmgr) lifecycle across macOS, Linux, and Windows. Covers start, stop, restart, status, enable/disable at boot, and version detection.

Execution Routing

Default execution order when REST or remote access is needed:

1. Local CLI execution — manage oplmgr via sudo commands, launchctl, or systemctl (primary mode)
2. URIBurner REST functions — for remote license server status checks or management
3. Terminal-owned OAuth flow — when a REST endpoint requires OAuth 2.0 authentication, execute the OAuth flow from the terminal (authorization code, client credentials, or device flow), capture the Bearer token, and inject it into subsequent REST/OpenAPI calls via Authorization: Bearer {token} headers
4. MCP — if a remote MCP-enabled service exposes license manager tools

If the user names a specific mode or protocol, follow that preference instead.

Step 0 — Detect OS and Init System

# Detect OS
uname -s   # Darwin = macOS, Linux = Linux
           # Windows: uname absent; detect via %OS% or assume Windows if neither works

# On Linux only — detect init system
systemctl --version 2>/dev/null && echo "systemd" || echo "manual"

If OS detection is ambiguous, ask the user to confirm their OS before proceeding.

Step 1 — Pre-flight Checks (macOS and Linux only)

Run these checks in order before attempting any privileged command. Claude Code runs non-interactively (no TTY), so both the symlink and passwordless sudo must be in place.

Check A — Symlink at /usr/local/bin/oplmgr

sudoers cannot handle paths containing spaces. The real binary lives at /Library/Application Support/openlink/bin/oplmgr, so a space-free symlink is required.

ls -la /usr/local/bin/oplmgr 2>/dev/null && echo "symlink OK" || echo "symlink MISSING"

If symlink is MISSING, attempt to create it automatically:

sudo ln -s "/Library/Application Support/openlink/bin/oplmgr" /usr/local/bin/oplmgr

• If this sudo succeeds (passwordless sudo already configured for another rule or user is root): proceed.
• If this sudo fails with a password prompt error: inform the user and ask them to run the command in Terminal.app:

  sudo ln -s "/Library/Application Support/openlink/bin/oplmgr" /usr/local/bin/oplmgr
  

  Then retry from the top of Step 1.

On Linux: no symlink is needed if the binary path already contains no spaces (e.g. /opt/openlink/oplmgr/oplmgr).

Check B — Passwordless sudo for /usr/local/bin/oplmgr

sudo -n /usr/local/bin/oplmgr +stop 2>&1; echo "exit:$?"
# exit:0 or a non-password error = passwordless sudo OK
# "sudo: a password is required" = NOT configured

If passwordless sudo is NOT configured, stop and inform the user:

Passwordless sudo is not configured for oplmgr. Please run the following in Terminal.app:

echo 'YOUR_USERNAME ALL=(ALL) NOPASSWD: /usr/local/bin/oplmgr' | sudo tee /etc/sudoers.d/oplmgr && sudo chmod 440 /etc/sudoers.d/oplmgr

On Linux (systemd), grant passwordless sudo for systemctl instead:

echo 'YOUR_USERNAME ALL=(ALL) NOPASSWD: /bin/systemctl start oplmgr.service, /bin/systemctl stop oplmgr.service, /bin/systemctl restart oplmgr.service, /bin/systemctl status oplmgr.service' | sudo tee /etc/sudoers.d/oplmgr && sudo chmod 440 /etc/sudoers.d/oplmgr

Then return here and retry.

Windows: no pre-flight checks needed — Administrator privilege is handled by the OS service manager.

Step 2 — Show Command and Confirm

Always display the exact command(s) that will be run and ask the user to confirm before executing.

Present the applicable command from the tables below, then proceed only on confirmation.

Step 3 — Command Reference by Platform

macOS

Priority 1 — Direct binary (preferred)

Try oplmgr from its installation directory first:

# Locate the binary (prefer symlink at /usr/local/bin/oplmgr)
which oplmgr 2>/dev/null || ls /usr/local/bin/oplmgr 2>/dev/null

Before starting, detect the version and derive and validate the +directory value:

# Step A: Detect version
/usr/local/bin/oplmgr 2>&1 | head -5

# Step B: Derive license directory
LICENSE_DIR="${OPL_LICENSE_DIR:-/Library/Application Support/openlink/Licenses}"

# Step C: Validate — directory must exist and contain at least one .lic file
ls "${LICENSE_DIR}"/*.lic 2>/dev/null | head -1

Decision table:

If no valid license directory is found, stop and inform the user:

No license directory could be found. Neither $OPL_LICENSE_DIR nor the default path (/Library/Application Support/openlink/Licenses/) exists or contains .lic files. Please provide the path to the directory containing your OpenLink license files, then retry.

Canonical binary location: /Library/Application Support/openlink/bin/oplmgr Symlink (no spaces — required for sudoers): /usr/local/bin/oplmgr

Important: Always use /usr/local/bin/oplmgr (the symlink) for sudo commands. The real path contains spaces which sudoers cannot handle.

Priority 2 — launchctl fallback (if binary unavailable or for boot persistence)

Note: If a non-default license directory is used, edit the plist at /Library/LaunchDaemons/com.openlinksw.oplmgr.plist to reflect the new path before loading.

Linux — systemd (preferred when available)

# Check for systemd
systemctl --version 2>/dev/null

Linux — Manual (no systemd)

Note: Installation path may vary. Common alternatives: /opt/openlink/bin/oplmgr, or per-product bin/ directories. Check $OPL_LICENSE_DIR for hints.

Windows

Administrator privileges are required for all service operations.

Priority 1 — PowerShell (preferred)

Priority 2 — net / sc (fallback)

On 64-bit Windows with mixed 32/64-bit installations: consolidate all license files in a single directory (e.g. C:\Program Files\OpenLink Software\Licenses\) to avoid bitness-mismatch issues with the registry lookup at: HKLM\SOFTWARE\OpenLink Software\License Manager\License Directories\

Step 4 — Version Detection and Behavioral Notes

oplmgr -?

Default license directories by version and OS:

Step 5 — Post-Action Status Check

After any start or stop action, automatically run the status command for the detected platform and display the result to confirm the operation succeeded.

Initialization Sequence

When invoked:

⛔ PRE-BUILD CHECK: Before producing output, re-read the relevant workflow section above and re-read any checklists or verification gates defined in this skill. Confirm each checklist item before writing output. Build to pass — do not retro-fit. Apply the CLAUDE.md Anti-Drift Protocol: re-read spec section before build, gate-first validation, section-by-section delivery.

1. Run Step 0 — detect OS and (on Linux) init system
2. Run Step 1, Check A — verify symlink exists; attempt to create it automatically if missing
3. Run Step 1, Check B — verify passwordless sudo; halt with setup instructions if not configured
4. Run Step 2 — show the relevant command(s) and ask for confirmation
5. Execute on confirmation — run the command
6. Run Step 5 — show status output

Troubleshooting

Version

1.5.0 — License directory validation added before +start on macOS/Linux: checks existence and presence of .lic files; halts with actionable message when $OPL_LICENSE_DIR is unset and the OS default path is missing or empty. Added troubleshooting row for +directory path missing or empty.

1.4.0 — macOS/Linux start now detects version and derives +directory value before issuing +start (v1.3.6+ only). Windows: PowerShell Start-Service/Stop-Service added as Priority 1; net/sc demoted to Priority 2 fallback.

1.3.0 — Step 1 now includes Check A (symlink detection + automatic creation attempt) before Check B (passwordless sudo). Skill self-heals the symlink when possible without user intervention.

1.2.0 — macOS commands now use /usr/local/bin/oplmgr symlink throughout (sudoers cannot handle paths with spaces). Setup instructions updated to include symlink creation step. Added expected a fully-qualified path name to troubleshooting table.

1.1.0 — Added passwordless sudo pre-check (Step 1) with setup instructions for macOS and Linux. Added sudo: a terminal is required to troubleshooting table.

1.0.0 — Initial release. macOS (binary + launchctl fallback), Linux (systemd + manual fallback), Windows (service). Version detection and behavioral notes for v1.3.5 vs v1.3.6+.