Configuration Parameters Reference

This section provides detailed configuration elements and operational parameters used in RADIUS and LDAP Auth Proxy setups.

---

Overview

These configurations are primarily managed through AdminX and underlying directory/server configurations.

RADIUS Configuration

Shared Secret (Radius Secret)

• A shared secret must be configured between:

  • RADIUS client

  • Auth Proxy (RADIUS server)

• This value must match exactly on both ends.

Server Communication

• The RADIUS client must be able to reach the Auth Proxy

• Network connectivity must be established between:

  • RADIUS client

  • Auth Proxy host

Execution

goauthproxy radius

Logs and Process Management

• Logs are generated during execution of the RADIUS server

• Each running instance is associated with a Process ID (PID)

Process management examples:

Linux / macOS:

ps -ef | grep goauthproxykill -9 <PID>

Windows:

tasklist | findstr goauthproxytaskkill /PID <PID> /F

---

LDAP Configuration

Configuration ID

• Generated when creating Auth Proxy configuration in AdminX

• Required to start LDAP Auth Proxy

---

Execution

goauthproxy ldap --configId <CONFIG_ID>

---

LDAP Server Connectivity

• LDAP server hostname must be reachable

• Required ports must be open

• Directory credentials must be valid

---

LDAP / LDAPS Parameters

LDAP configuration includes:

• Hostname of LDAP server

• LDAP or LDAPS port

• Bind credentials

• Connection settings

---

Hostname Failover

• Multiple LDAP servers can be configured

• If primary server is unavailable:

  • Auth Proxy attempts next configured server

---

Logs and Process Management

• Logs are generated during execution

• Process is identified using PID

Process management examples:

Linux / macOS:

ps -ef | grep goauthproxykill -9 <PID>

Windows:

tasklist | findstr goauthproxytaskkill /PID <PID> /F

---

Authentication Methods

The following authentication methods are supported:

• Push Authentication

• Interactive Voice Response (IVR)

• Passcodes

These methods are configured through AdminX

• Configuration is split between AdminX (control plane) and the Auth Proxy runtime (CLI execution).

• Ensure system time is synchronized for passcode-based authentication.