openstack
/
barbican
Code Issues Proposed changes

Fix crypto plugin documentation 

Changes references from barbican.plugin.crypto.crypto to
barbican.plugin.crypto.base.

Change-Id: I1461ef876aa670cd856a339d1cf8d29e410f5576
This commit is contained in:
Kaitlin Farr 2016-11-15 17:49:02 -05:00
parent 30bbeae8eb
commit ed124cbe2e
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/plugin/crypto.rst
View File

@ -1,4 +1,4 @@
.. module:: barbican.plugin.crypto.crypto
.. module:: barbican.plugin.crypto.base
================================
Cryptographic Plugin Development
@ -67,7 +67,7 @@ described in :ref:`plugin-secret-store-crypto-adapter-label`.
**For secret storage actions**, Barbican core calls the following methods:
1. ``supports()`` - Asks the plugin if it can support the
``barbican.plugin.crypto.crypto.PluginSupportTypes.ENCRYPT_DECRYPT``
``barbican.plugin.crypto.base.PluginSupportTypes.ENCRYPT_DECRYPT``
operation type.
2. ``bind_kek_metadata()`` - Allows a plugin to bind an internal key encryption
@ -91,7 +91,7 @@ as the project-ID KEK used to encrypt the secret.
**For symmetric key generation**, Barbican core calls the following methods:
1. ``supports()`` - Asks the plugin if it can support the
``barbican.plugin.crypto.crypto.PluginSupportTypes.SYMMETRIC_KEY_GENERATION``
``barbican.plugin.crypto.base.PluginSupportTypes.SYMMETRIC_KEY_GENERATION``
operation type.
2. ``bind_kek_metadata()`` - Same comments as for secret storage above.
@ -103,7 +103,7 @@ as the project-ID KEK used to encrypt the secret.
**For asymmetric key generation**, Barbican core calls the following methods:
1. ``supports()`` - Asks the plugin if it can support the
``barbican.plugin.crypto.crypto.PluginSupportTypes.ASYMMETRIC_KEY_GENERATION``
``barbican.plugin.crypto.base.PluginSupportTypes.ASYMMETRIC_KEY_GENERATION``
operation type.
2. ``bind_kek_metadata()`` - Same comments as for secret storage above.