Update introduction of external services doc

This document is written for other developers working on OpenStack.
Its goal is to describe various concepts in a way that other
developers, who may not be familiar with keystone, can digest and use
effectively in their projects.

The introductory paragraph was phrased as if the v3 API just became a
thing, when it has actually been around for a long time. It also
eluded to underlying implementation details by mentioning paste
pipelines, which we no longer use.

This commit updates the introduction to be more relevant to the state
of things today.

Change-Id: I79564dc99fd65a5609bd548d12a0413ca3ee6b2a
This commit is contained in:
Lance Bragstad 2019-02-22 00:48:29 +00:00
parent ace4584194
commit 4d2a219a3b
1 changed files with 2 additions and 7 deletions

View File

@ -17,13 +17,8 @@ Keystone for other services
This document provides a summary of some things that other services need to
know about how keystone works, and specifically about how they can take
advantage of the v3 API.
The v3 API was introduced as a stable API in the Grizzly release and included
in the default pipeline ever since. Until recently, its use has been hidden
from other services because the ``auth_token`` middleware translated the token
format so that both versions look the same. Once the services need to make use
of v3 features they need to know about how it works.
advantage of the v3 API. The v3 API was introduced as a stable API in the
Grizzly release.
Glossary