> For the complete documentation index, see [llms.txt](https://hayston.gitbook.io/flp-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hayston.gitbook.io/flp-wiki/compatibility-and-integrations/auth-plugins.md).

# Other authentication plugins

## Available integrations

| Platform     | Authentication plugins                                                                |
| ------------ | ------------------------------------------------------------------------------------- |
| Bukkit/Folia | AuthMe, CrazyLogin, LogIt, LoginSecurity, UltraAuth, xAuth, Passky                    |
| BungeeCord   | BungeeAuth                                                                            |
| Velocity     | Install an authentication plugin on participating backends                            |
| Fabric       | EasyAuth; see the [Fabric installation guide](/flp-wiki/install-and-deploy/fabric.md) |

This list does not guarantee every plugin version is compatible with your server. Check each plugin's requirements and startup log, then check login with test accounts before opening the server. Prefer one authentication plugin per backend.

## Capabilities are not interchangeable

Automatic registration, login and account switching vary by authentication plugin; do not assume they behave like AuthMe. If a plugin generated a player's password, switching back to password login may require that plugin's own recovery procedure.

Folia requires the auth plugin itself to support Folia. Moving from Bukkit FLP to Folia FLP does not adapt another plugin's scheduler calls.

The BungeeAuth hook is separate from backend AuthMe and does not create a native proxy `/flp` management command. Do not combine multiple independent auto-login systems without a clear ownership and identity model.

If a plugin is incompatible or fails to start, keep the logs and [report the problem](/flp-wiki/operations-and-troubleshooting/reporting.md) rather than removing safety checks.


---

# 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://hayston.gitbook.io/flp-wiki/compatibility-and-integrations/auth-plugins.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.