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

# Authentication

> User Authentication

Currently, Seldon Enterprise Platform SSO can be configured in two ways.

* [Kubeflow cluster](https://www.kubeflow.org)
* [App-level authentication](/seldon-enterprise-platform/production-environment/auth.md)

## App-level Auth

App-level auth is where a request to Seldon Enterprise Platform is checked for an auth token and if that is missing then the application redirects to the auth system.

Enterprise Platform uses OIDC and can be integrated to OIDC auth systems.

## Kubeflow Gateway Auth

In the Kubeflow architecture, the auth is done at gateway level before reaching Enterprise Platform or any other apps:

![existing\_arrikto](/files/kz2k2d67DQCRGa418dCT)

This 'existing\_arrikto' architecture uses an Envoy filter in Istio to run all requests through a check for an auth token, performed by the OIDC AuthService. If no token is available then the user is sent to dex to login and obtain a token.

LDAP, or another external identity provider, can be used as per the existing\_arrikto example and in line with the dex documentation.

In order to enforce restrictions, namespaces for Seldon Enterprise Platform are labelled as restricted or unrestricted and with the operations that groups can perform on them. See the [namespace setup documentation](/seldon-enterprise-platform/operations/namespace-setup.md#namespace-detection) for further 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.seldon.ai/seldon-enterprise-platform/architecture/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.