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

# Authentication

Unimarket offers several authentication mechanisms to provide flexibility for different security and user management needs. These fall into two main categories: **Username/Password Authentication** and **Single Sign-On (SSO)**.

## Username / Password Authentication

These methods involve users entering credentials into a login screen, which are then verified against Unimarket or an external database.

* **Standard Unimarket Authentication**: The default method where users and passwords are created and stored directly in Unimarket. No external setup is required.
* **Active Directory (LDAP) Authentication**: Users enter their credentials on the Unimarket login page, but Unimarket sends a request to the customer's Active Directory server to verify them.
  * **Benefit**: Centralized control — removing a user from AD automatically blocks their Unimarket access.
  * **Note**: Requires opening standard LDAP/LDAPS ports in the customer firewall.
* **Integrated Username/Password (SOAP)**: Credentials entered in Unimarket are sent via a SOAP web service request to a custom endpoint in the customer's environment. This provides full control over custom backend integrations.

## Single Sign-On (SSO) Authentication

[SSO](/documentation/authentication-and-users/setting-up-saml-sso.md) allows users to access Unimarket without re-entering credentials, if they are already authenticated within their organization's network or portal.

| SSO Method                                                                                 | Description                              | Key Features                                                                                                                                          |
| ------------------------------------------------------------------------------------------ | ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| [SAML](https://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html) | Industry-standard XML-based framework.   | Unimarket acts as the Service Provider (SP) and integrates with the customer's Identity Provider (IDP). Can include roles and groups in the response. |
| [CAS](https://www.apereo.org/programs/software/cas)                                        | Central Authentication Service standard. | Allows transparent authentication through the CAS protocol.                                                                                           |
| Unimarket Integrated                                                                       | Custom web service integration.          | Documentation-heavy setup for highly customized portal environments.                                                                                  |

## Key Comparison: User Management

Regardless of the authentication method chosen, user profiles (roles, buyer groups, and org units) must still be managed. This can be done in two ways:

1. **Manual/Admin Management**: A Unimarket Administrator manually configures roles and settings within the application.
2. **Integrated Management**: Using the Unimarket User-Detail integration to externally sync profile details or, in the case of SAML, passing attributes directly in the authentication response.

## What's Next/Related

* [Firewall Requirements](https://help.unimarket.com/hc/en-us/articles/45852280196761-Firewall-Requirements)


---

# 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.unimarket.com/documentation/authentication-and-users/authentication.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.