Update docs to no longer show XML support
implements bp removed-as-of-kilo Change-Id: Ib78132093cc0ab9b964013b20734ada1039f0679
This commit is contained in:
parent
7f52036bd4
commit
5d376ba9ad
|
@ -782,10 +782,6 @@ Returns:
|
|||
},
|
||||
],
|
||||
"media-types":[
|
||||
{
|
||||
"base":"application/xml",
|
||||
"type":"application/vnd.openstack.identity-v2.0+xml"
|
||||
},
|
||||
{
|
||||
"base":"application/json",
|
||||
"type":"application/vnd.openstack.identity-v2.0+json"
|
||||
|
|
|
@ -79,7 +79,7 @@ of pipelines of WSGI middleware, such as:
|
|||
|
||||
[pipeline:api_v3]
|
||||
pipeline = sizelimit url_normalize build_auth_context token_auth admin_token_auth
|
||||
xml_body_v3 json_body ec2_extension_v3 s3_extension service_v3
|
||||
json_body ec2_extension_v3 s3_extension service_v3
|
||||
|
||||
These in turn use a subclass of :mod:`keystone.common.wsgi.ComposingRouter` to
|
||||
link URLs to Controllers (a subclass of
|
||||
|
|
|
@ -830,7 +830,7 @@ and before the ``public_service`` app in the public_api WSGI pipeline in
|
|||
paste.filter_factory = keystone.contrib.user_crud:CrudExtension.factory
|
||||
|
||||
[pipeline:public_api]
|
||||
pipeline = url_normalize token_auth admin_token_auth xml_body json_body debug ec2_extension user_crud_extension public_service
|
||||
pipeline = url_normalize token_auth admin_token_auth json_body debug ec2_extension user_crud_extension public_service
|
||||
|
||||
Each user can then change their own password with a HTTP PATCH :
|
||||
|
||||
|
|
|
@ -31,7 +31,7 @@ To enable the endpoint filter extension:
|
|||
the last entry in the pipeline. For example::
|
||||
|
||||
[pipeline:api_v3]
|
||||
pipeline = sizelimit url_normalize build_auth_context token_auth admin_token_auth xml_body_v3 json_body ec2_extension_v3 s3_extension simple_cert_extension revoke_extension endpoint_filter_extension service_v3
|
||||
pipeline = sizelimit url_normalize build_auth_context token_auth admin_token_auth json_body ec2_extension_v3 s3_extension simple_cert_extension revoke_extension endpoint_filter_extension service_v3
|
||||
|
||||
3. Create the endpoint filter extension tables if using the provided sql backend. For example::
|
||||
|
||||
|
|
|
@ -28,7 +28,7 @@ To enable the endpoint policy extension:
|
|||
the last entry in the pipeline. For example::
|
||||
|
||||
[pipeline:api_v3]
|
||||
pipeline = sizelimit url_normalize build_auth_context token_auth admin_token_auth xml_body_v3 json_body ec2_extension_v3 s3_extension simple_cert_extension revoke_extension service_v3 endpoint_policy_extension service_v3
|
||||
pipeline = sizelimit url_normalize build_auth_context token_auth admin_token_auth json_body ec2_extension_v3 s3_extension simple_cert_extension revoke_extension service_v3 endpoint_policy_extension service_v3
|
||||
|
||||
3. Create the endpoint policy extension tables if using the provided SQL backend. For example::
|
||||
|
||||
|
|
|
@ -44,7 +44,7 @@ To enable the federation extension:
|
|||
the last entry in the pipeline. For example::
|
||||
|
||||
[pipeline:api_v3]
|
||||
pipeline = sizelimit url_normalize build_auth_context token_auth admin_token_auth xml_body_v3 json_body ec2_extension_v3 s3_extension simple_cert_extension revoke_extension federation_extension service_v3
|
||||
pipeline = sizelimit url_normalize build_auth_context token_auth admin_token_auth json_body ec2_extension_v3 s3_extension simple_cert_extension revoke_extension federation_extension service_v3
|
||||
|
||||
4. Create the federation extension tables if using the provided SQL backend.
|
||||
For example::
|
||||
|
|
|
@ -36,7 +36,7 @@ To enable the OAuth1 extension:
|
|||
the last entry in the pipeline. For example::
|
||||
|
||||
[pipeline:api_v3]
|
||||
pipeline = sizelimit url_normalize build_auth_context token_auth admin_token_auth xml_body_v3 json_body ec2_extension_v3 s3_extension simple_cert_extension revoke_extension oauth1_extension service_v3
|
||||
pipeline = sizelimit url_normalize build_auth_context token_auth admin_token_auth json_body ec2_extension_v3 s3_extension simple_cert_extension revoke_extension oauth1_extension service_v3
|
||||
|
||||
4. Create the OAuth1 extension tables if using the provided SQL backend. For example::
|
||||
|
||||
|
|
|
@ -37,7 +37,7 @@ Enabling the Revocation Extension
|
|||
paste.filter_factory = keystone.contrib.revoke.routers:RevokeExtension.factory
|
||||
|
||||
[pipeline:api_v3]
|
||||
pipeline = sizelimit url_normalize build_auth_context token_auth admin_token_auth xml_body_v3 json_body ec2_extension_v3 s3_extension simple_cert_extension revoke_extension service_v3
|
||||
pipeline = sizelimit url_normalize build_auth_context token_auth admin_token_auth json_body ec2_extension_v3 s3_extension simple_cert_extension revoke_extension service_v3
|
||||
|
||||
3. Create the revocation extension tables if using the provided SQL backend.
|
||||
For example::
|
||||
|
|
|
@ -147,9 +147,9 @@ authentication.
|
|||
For example, if the original pipeline looks like this::
|
||||
|
||||
[pipeline:public_api]
|
||||
pipeline = url_normalize token_auth admin_token_auth xml_body json_body debug ec2_extension user_crud_extension public_service
|
||||
pipeline = url_normalize token_auth admin_token_auth json_body debug ec2_extension user_crud_extension public_service
|
||||
|
||||
Your modified pipeline might then look like this::
|
||||
|
||||
[pipeline:public_api]
|
||||
pipeline = url_normalize token_auth admin_token_auth xml_body json_body my_auth debug ec2_extension user_crud_extension public_service
|
||||
pipeline = url_normalize token_auth admin_token_auth json_body my_auth debug ec2_extension user_crud_extension public_service
|
||||
|
|
Loading…
Reference in New Issue