Fix some typo in releasenotes
Change-Id: Ief47447ff7213d6813fd8a09a5d630972df23fef
This commit is contained in:
parent
1d4c72cd6f
commit
6168e3afc1
@ -4,7 +4,7 @@ features:
|
||||
[`blueprint shadow-mapping <https://blueprints.launchpad.net/keystone/+spec/shadow-mapping>`_]
|
||||
The federated identity mapping engine now supports the ability to
|
||||
automatically provision ``projects`` for ``federated users``. A role assignment
|
||||
will automatically be created for the user on the specificed proejct. If the
|
||||
will automatically be created for the user on the specified project. If the
|
||||
project specified within the mapping does not exist, it will be automatically
|
||||
created in the ``domain`` associated with the ``identity provider``.
|
||||
This behavior can be triggered using a specific syntax within the ``local``
|
||||
|
@ -3,5 +3,5 @@ features:
|
||||
- >
|
||||
[`blueprint support-federated-attr <https://blueprints.launchpad.net/keystone/+spec/support-federated-attr>`_]
|
||||
Added new filters to the `list user` API (``GET /v3/users``) to support
|
||||
querying federated identity atttributes: ``idp_id``, ``protocol_id``, and
|
||||
querying federated identity attributes: ``idp_id``, ``protocol_id``, and
|
||||
``unique_id``.
|
||||
|
@ -5,6 +5,6 @@ fixes:
|
||||
New option ``[ldap] connection_timeout`` allows a deployer to set a
|
||||
``OPT_NETWORK_TIMEOUT`` value to use with the LDAP server.
|
||||
This allows the LDAP server to return a ``SERVER_DOWN`` exception,
|
||||
if the LDAP URL is incorrect if there is a connection failure. By default,
|
||||
if the LDAP URL is incorrect or if there is a connection failure. By default,
|
||||
the value for ``[ldap] connection_timeout`` is -1, meaning it is disabled.
|
||||
Set a postive value (in seconds) to enable the option.
|
||||
Set a positive value (in seconds) to enable the option.
|
||||
|
@ -4,7 +4,7 @@ features:
|
||||
allows to trace various requests through all OpenStack
|
||||
services that support it. To initiate OpenStack
|
||||
request tracing `--profile <HMAC_KEY>` option needs to be added to
|
||||
the CLI command. Configuration and usage details can be foung in
|
||||
the CLI command. Configuration and usage details can be found in
|
||||
[`OSProfiler documentation <https://docs.openstack.org/developer/osprofiler/api.html>`_]
|
||||
upgrade:
|
||||
- OSprofiler support was introduced. To allow its usage the
|
||||
|
Loading…
Reference in New Issue
Block a user