> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/authentication/authentication-broker/configuration-parameters-reference.md).

# Configuration Parameters Reference

***

### 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

```bash
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

{% hint style="info" %}

* Configuration is split between AdminX (control plane) and the Auth Proxy runtime (CLI execution).
* Ensure system time is synchronized for passcode-based authentication.
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.1kosmos.com/authentication/authentication-broker/configuration-parameters-reference.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.