Line 3:
Line 3: * 支援其使用於包含專案級別 keys的輪轉主要key。在這種輕量級的方法，只有專案級別key (KEK) 是re-wrapped 新的主要的key (MKEK)。目前只適用於 PKCS11 plug-in 。(http://specs.openstack.org/openstack/barbican-specs/specs/liberty/add-crypto-mkek-rotation-support-lightweight.html)
* 支援其使用於包含專案級別 keys的輪轉主要key。在這種輕量級的方法，只有專案級別key (KEK) 是re-wrapped 新的主要的key (MKEK)。目前只適用於 PKCS11 plug-in 。(http://specs.openstack.org/openstack/barbican-specs/specs/liberty/add-crypto-mkek-rotation-support-lightweight.html)
* 更新Barbican's root資源返回版本訊息符合Keystone, Nova 和 Manila 格式。這是使用keystoneclient's的版本端點查詢功能。
* 更新Barbican's root資源返回版本訊息符合Keystone, Nova 和 Manila 格式。這是使用keystoneclient's的版本端點查詢功能。
− * Removed administrator endpoint as all operations are available on a regular endpoint. No separate endpoint is needed as access restrictions are enforced via Oslo policy.
+ * 移除管理員對任何一端點的所有操作。不需要單獨終端訪問權限是透過Oslo進行管理 .
− * Added configuration for enabling sqlalchemy pool for the management of SQL connections.
+ * 新增對啟用sqlalchemy pool連接SQL管理配置。
− * Added ability to list secrets which are accessible via ACL using GET /v1/secrets?acl-only=true request.
+ * 新增功能列出secrets，透過使用GET /v1/secrets?acl-only=true 訪問ACL。
− * Improved functional test coverage around Barbican APIs related to ACL operations, RBAC policy and secrets.
+ * 改進功能測試覆蓋率，圍繞著有關ACL操作Barbican APIs，RBAC政策和secret
− * Fixed issues around creation of SnakeOil CA plug-in instance.
+ * 修復創建SnakeOil CA plug-in instance問題
− * Barbican client CLI can now take a Keystone token for authentication. Earlier only username and password based authentication was supported.
+ * Barbican client CLI 現在可以採取Keystone token認證。支援在以前唯一的使用者名稱和密碼認證
− * Barbican client now has ability to create and list certificate orders.
+ * Barbican client 現在有能裡創建和列表憑證命令
Information about message (contribute ) This message has no documentation.
If you know where or how this message is used, you can help other translators by adding documentation to this message.
Message definition (ReleaseNotes/Liberty )
* Added the ability for project administrators to create certificate authorities per project. Also, project administrators are able to define and manage a set of preferred certificate authorities (CAs) per project. This allows projects to achieve project specific security domains.
* Added the ability for project administrators to create certificate authorities per project. Also, project administrators are able to define and manage a set of preferred certificate authorities (CAs) per project. This allows projects to achieve project specific security domains.
* Barbican now has per project quota support for limiting number of Barbican resources that can be created under a project. By default the quota is set to unlimited and can be overridden in Barbican configuration.
* Support for a rotating master key which is used for wrapping project level keys. In this lightweight approach, only the project level key (KEK) is re-wrapped with new master key (MKEK). This is currently applicable only for the PKCS11 plug-in. (http://specs.openstack.org/openstack/barbican-specs/specs/liberty/add-crypto-mkek-rotation-support-lightweight.html)
* Updated Barbican's root resource to return version information matching Keystone, Nova and Manila format. This is used by keystoneclient's versioned endpoint discovery feature.
* Removed administrator endpoint as all operations are available on a regular endpoint. No separate endpoint is needed as access restrictions are enforced via Oslo policy.
* Added configuration for enabling sqlalchemy pool for the management of SQL connections.
* Added ability to list secrets which are accessible via ACL using GET /v1/secrets?acl-only=true request.
* Improved functional test coverage around Barbican APIs related to ACL operations, RBAC policy and secrets.
* Fixed issues around creation of SnakeOil CA plug-in instance.
* Barbican client CLI can now take a Keystone token for authentication. Earlier only username and password based authentication was supported.
* Barbican client now has ability to create and list certificate orders. Translation * 新增專案管理員能力去創建每個專案憑證授權。此外, 專案管理員能夠定義和管理每一個專案優先憑證配發機構(CAs)。讓允許專案實現特定安全性domains 
