mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-24 23:27:25 -04:00
255c9a7f95
**Problem:** For historical reasons, source files for the Elasticsearch Guide's security, watcher, and Logstash API docs are housed in the `x-pack/docs` directory. This can confuse new contributors who expect Elasticsearch Guide docs to be located in `docs/reference`. **Solution:** - Move the security, watcher, and Logstash API doc source files to the `docs/reference` directory - Update doc snippet tests to use security Rel: https://github.com/elastic/platform-docs-team/issues/208
19 lines
882 B
Text
19 lines
882 B
Text
[role="xpack"]
|
|
[[oidc-realm]]
|
|
=== OpenID Connect authentication
|
|
|
|
The OpenID Connect realm enables {es} to serve as an OpenID Connect Relying
|
|
Party (RP) and provides single sign-on (SSO) support in {kib}.
|
|
|
|
It is specifically designed to support authentication via an interactive web
|
|
browser, so it does not operate as a standard authentication realm. Instead,
|
|
there are {kib} and {es} {security-features} that work together to enable
|
|
interactive OpenID Connect sessions.
|
|
|
|
This means that the OpenID Connect realm is not suitable for use by standard
|
|
REST clients. If you configure an OpenID Connect realm for use in {kib}, you
|
|
should also configure another realm, such as the <<native-realm, native realm>>
|
|
in your authentication chain.
|
|
|
|
In order to simplify the process of configuring OpenID Connect authentication
|
|
within the {stack}, there is a step-by-step guide: <<oidc-guide>>.
|