> 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-proxy/faqs.md).

# FAQs

<details>

<summary><strong>Which operating systems and version are supported?</strong> </summary>

A 64-bit operating system (Windows, macOS, or Linux), with at least 4 GB of RAM. The supported version is `goauthproxy 1.00.07`.

</details>

<details>

<summary><strong>Do I need the Config ID?</strong> </summary>

Yes. Remember the config ID from AdminX — it is required to run the Auth Proxy for RADIUS/LDAP and must be passed as the `-u <uuid>` parameter. The UUID and Config ID must match for the server to work.

</details>

<details>

<summary><strong>How long do configuration changes take to apply?</strong> </summary>

The wait time for changes to take effect is 10 minutes.

</details>

<details>

<summary><strong>What happens after I delete a configuration?</strong> </summary>

After removing the configuration, users cannot authenticate using the deleted Config ID.

</details>

<details>

<summary><strong>Can a single GoAuthProxy instance run multiple LDAP/LDAPS servers at the same time?</strong> </summary>

No. A single GoAuthProxy instance does not currently support multiple LDAP/LDAPS servers simultaneously.

</details>

<details>

<summary><strong>Do I need root access to run LDAP on low ports?</strong> </summary>

On Linux and macOS, root access is required to run servers on ports below 1024, including LDAP on port 389 and LDAPS on port 636.

</details>

<details>

<summary><strong>Can I run RADIUS and LDAP together?</strong> </summary>

Yes. The `-r` parameter can be used together with the LDAP `-l` parameter; setting `-r true` starts the RADIUS server along with the LDAP server.

</details>

<details>

<summary><strong>What are the default RADIUS port and secret?</strong> </summary>

The default RADIUS port is 1812 and the default secret is `secret`. The default secret should only be used for testing; production servers should always use a secure secret string.

</details>

<details>

<summary><strong>What is the maximum length of the RADIUS shared secret?</strong> </summary>

The maximum length is 256 bytes, it is case sensitive, and a length of at least 16 characters is recommended.

</details>

<details>

<summary><strong>How do I handle special characters in the RADIUS secret?</strong> </summary>

If the secret contains bash shell special characters (`$`, `(`, `)`, …), escape it so bash does not interpret the characters as shell commands — for example, `secret$pecialchar(12)`.

</details>

<details>

<summary><strong>Which events are generated?</strong> </summary>

RADIUS authentication generates `E_LOGIN_SUCCEEDED` and `E_LOGIN_FAILED` events. Host availability changes generate an `E_HOSTNAME_STATUSCHANGE` event.

</details>

<details>

<summary><strong>How often are host availability notification emails sent?</strong> </summary>

If a host is reported as inactive and a notification email is sent, additional emails for the same host are suppressed for the next five minutes.

</details>


---

# 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-proxy/faqs.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.