> 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/passwordless-for-linux-ssh/adminx-configuration.md).

# AdminX Configuration

Journeys let you control which authentication factors are required based on who the user is or which group they belong to. By default, a new journey applies to all users.

***

### How to Configure

Adaptive Auth Journeys for Linux PAM are configured in AdminX under **Applications > Linux PAM > Adaptive Auth Journeys**. 

### Creating an Authentication Journey

Click **Add new adaptive auth journey**, give it a name, and set it to enabled or disabled.

**Conditions** — define who the journey applies to:

| Category | Operators                                                                                                                   |
| -------- | --------------------------------------------------------------------------------------------------------------------------- |
| Groups   | Is one of / Is not one of / Contains / Does not contain                                                                     |
| Username | Is one of / Is not one of / Contains / Does not contain / Starts with / Does not start with / Ends with / Does not end with |

**Actions** — define what happens when conditions are matched:

| Action           | Behavior                                                                                                                                                                                             |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Grant Access** | User is granted access without any MFA prompts. Use this only alongside LDAP PAM for service accounts — using it with 1Kosmos PAM alone allows login with just a username, which is a security risk. |
| **Deny Access**  | Access is denied and the user sees: "Login failed due to max number of authentication attempts."                                                                                                     |
| **MFA Required** | User must complete one or more of the selected factors before access is granted.                                                                                                                     |

**MFA Required** supports the following factor options:

* Just Password
* Push Notification
* 1Kosmos App Codes
* Any OTP (mobile TOTP, email OTP, SMS OTP, phone OTP)
* SMS OTP (requires registered mobile number)
* Email OTP (requires registered email)
* Voice OTP (requires registered phone/landline)
* Password + Push Notification
* Password + 1Kosmos App Codes
* Password + Any OTP
* Password + SMS OTP
* Password + Email OTP
* Password + Voice OTP

Click **Save** to apply the journey.

### Deleting an Authentication Journey

In the **Adaptive Auth Journeys** list, click the **delete icon** next to the journey you want to remove.


---

# 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/passwordless-for-linux-ssh/adminx-configuration.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.