Remove extension and auth_token middleware docs

* We do not use extensions any longer, everything is core all
  the time.

* keystonemiddleware has been a thing for a long time, lets
  remove the doc that links back to it.

Change-Id: Id51f5d6f09c65a15908cb6e7964336ba680241d4
This commit is contained in:
Steve Martinelli 2016-11-18 15:47:37 -05:00
parent 4c5b15e3db
commit deeb8df7cd
3 changed files with 0 additions and 81 deletions

View File

@ -1,45 +0,0 @@
..
Licensed under the Apache License, Version 2.0 (the "License"); you may
not use this file except in compliance with the License. You may obtain
a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations
under the License.
==========
Extensions
==========
Status
======
An extension may be considered ``stable``, ``experimental`` or ``out-of-tree``.
* A `stable` status indicates that an extension is fully supported by the
OpenStack Identity team.
* An `experimental` status indicates that although the intention is to keep
the API unchanged, we reserve the right to change it up until the point that
it is deemed `stable`.
* An `out-of-tree` status indicates that no formal support will be provided.
Graduation Process
==================
By default, major new functionality that is proposed to be in-tree will start
off in `experimental` status. Typically it would take at minimum of one cycle
to transition from `experimental` to `stable`, although in special cases this
might happened within a cycle.
Removal Process
===============
It is not intended that functionality should stay in experimental for a long
period, functionality that stays `experimental` for more than **two** releases
would be expected to make a transition to either `stable` or `out-of-tree`.

View File

@ -55,7 +55,6 @@ Getting Started
apache-httpd
architecture
policy_mapping
extensions
community
Configuration
@ -91,7 +90,6 @@ Developers Documentation
developing
developing_drivers
api_change_tutorial
middlewarearchitecture
http-api
api_curl_examples
services

View File

@ -1,34 +0,0 @@
..
Copyright 2011-2012 OpenStack Foundation
All Rights Reserved.
Licensed under the Apache License, Version 2.0 (the "License"); you may
not use this file except in compliance with the License. You may obtain
a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations
under the License.
=======================
Middleware Architecture
=======================
Abstract
========
The Keystone middleware architecture supports a common authentication protocol
in use between the OpenStack projects. By using Keystone as a common
authentication and authorization mechanism, the OpenStack project can plug in
to existing authentication and authorization systems in use by existing
environments.
The auth_token middleware is no longer hosted in Keystone and has moved to the
keystonemiddleware project. The `documentation regarding authentication
middleware`_ can be found there.
.. _`documentation regarding authentication middleware`: http://docs.openstack.org/developer/keystonemiddleware/middlewarearchitecture.html