> 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/authentication-methods-push-otp-ivr.md).

# Authentication Methods (Push, OTP, IVR)

***

The Auth Proxy server supports the following authentication methods for login. Community administrators configure which methods are permitted:

* Push Authentication
* Interactive Voice Response (IVR)
* Passcodes (OTP, Password and OTP, OTP and Password)
* Default Login Methods (RADIUS only): Push, Phone

### Login with Push

When enabled, users authenticate to their RADIUS or LDAP client by sending a push notification to their mobile device using the 1Kosmos Mobile Application. Instead of entering a password, users enter the keyword **push**, which triggers a push notification to their 1Kosmos mobile app. Users authenticate the push notification using their enrolled biometrics, such as a fingerprint or face scan.

* To enable, check the **Login with Push** box.
* To disable, uncheck the **Login with Push** box.

### Login with Interactive Voice Response (IVR)

When enabled, users authenticate their RADIUS or LDAP client using IVR on their mobile device. They provide their identifier (username for RADIUS, or distinguishedName for LDAP) along with the keyword **phone** in the password field. This initiates a phone call to the user's registered number, where they are prompted to press a specified button on the IVR to authorize authentication.

### Login with passcodes (OTP)

Administrators enable and define which one-time passcode (OTP) combinations can be used. Select from the following options:

* **Not supported** — users cannot log in using passcodes.
* **Prompt for OTP only** — when prompted for a password, the user provides only the 6-digit passcode.
* **Prompt for Password and OTP** — the user provides the password with the 6-digit passcode appended to the end. Example: `MyP@ssw0rd873174`.
* **Prompt for OTP and Password** — the user provides the password with the 6-digit passcode prepended before it. Example: `873174MyP@ssw0rd`.

### Default Login Methods (RADIUS only)

When no credentials are provided over RADIUS, the system can automatically trigger an authentication method:

* **Push** — sends a push notification to the user's biometrics-enabled device through the 1Kosmos Mobile Application; the user approves with their enrolled biometrics.
* **Phone** — initiates a phone call to the user's registered number using IVR; the user follows the IVR instructions to approve.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.1kosmos.com/authentication/authentication-proxy/authentication-methods-push-otp-ivr.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.