Fixed several typos
Change-Id: I006634a4b02cea488ff69967a599ea2dfc20fcd7
This commit is contained in:
@@ -335,7 +335,7 @@ class CryptoExtensionManager(named.NamedExtensionManager):
|
||||
|
||||
def generate_asymmetric_encryption_keys(self, meta, content_type, tenant,
|
||||
kek_repo):
|
||||
"""Delegates generating a asymmteric keys to the first
|
||||
"""Delegates generating asymmteric keys to the first
|
||||
supported plugin based on `meta`. meta will provide extra
|
||||
information to help key generation.
|
||||
Based on passpharse in meta this method will return a tuple
|
||||
|
||||
@@ -136,7 +136,7 @@ class GenerateDTO(object):
|
||||
String attribute used to identify the type of secret that should be
|
||||
generated. This will be either ``"symmetric"`` or ``"asymmetric"``.
|
||||
|
||||
.. attribute:: algoritm
|
||||
.. attribute:: algorithm
|
||||
|
||||
String attribute used to specify what type of algorithm the secret will
|
||||
be used for. e.g. ``"AES"`` for a ``"symmetric"`` type, or ``"RSA"``
|
||||
|
||||
@@ -382,7 +382,7 @@ class BaseRepo(object):
|
||||
def _do_validate(self, values):
|
||||
"""Sub-class hook: validate values.
|
||||
|
||||
Validates the incoming data and raises a Invalid exception
|
||||
Validates the incoming data and raises an Invalid exception
|
||||
if anything is out of order.
|
||||
|
||||
:param values: Mapping of entity metadata to check
|
||||
|
||||
@@ -11,7 +11,7 @@
|
||||
<representation mediaType="application/json"/>
|
||||
</response>
|
||||
<response status="400" xmlns="http://wadl.dev.java.net/2009/02">
|
||||
<doc title="Error">A general error occured.</doc>
|
||||
<doc title="Error">A general error occurred.</doc>
|
||||
<representation mediaType="application/xml" element="identity:badRequest"/>
|
||||
<representation mediaType="application/json"/>
|
||||
</response>
|
||||
|
||||
@@ -170,7 +170,7 @@
|
||||
<parameter>payload</parameter> parameter against the
|
||||
secrets resource and then include the payload in a
|
||||
subsequent <command>PUT</command> request. This mode
|
||||
enables you to upload a a binary file to the Barbican
|
||||
enables you to upload a binary file to the Barbican
|
||||
database directly for encrypted storage.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
@@ -567,7 +567,7 @@
|
||||
</para>
|
||||
<section xml:id="Generating_Order">
|
||||
<title>Generating an order</title>
|
||||
<para>This section describes how to generate an order throught
|
||||
<para>This section describes how to generate an order through
|
||||
the Barbican API.</para>
|
||||
<para>
|
||||
<orderedlist>
|
||||
|
||||
@@ -606,7 +606,7 @@
|
||||
specifying the secret payload and then
|
||||
submitting a subsequent <command>PUT</command>
|
||||
request with the payload. This storage mode
|
||||
enables you to upload a a binary file to the
|
||||
enables you to upload a binary file to the
|
||||
Barbican database directly for encrypted
|
||||
storage. For more information, read <olink
|
||||
targetdoc="ck-devguide"
|
||||
@@ -783,7 +783,7 @@
|
||||
<para>
|
||||
<programlisting>curl -i -H 'Content-Type: application/json' -d '{"name": "Binary Key File"}' http://<replaceable>endpointURL</replaceable>/v1/12345/secrets</programlisting>
|
||||
</para>
|
||||
<para>If the call is successfull, you receive
|
||||
<para>If the call is successful, you receive
|
||||
a <code>200 OK</code> response as shown in
|
||||
the following example:</para>
|
||||
<para>
|
||||
|
||||
@@ -163,7 +163,7 @@
|
||||
provided, only the secret metadata will be
|
||||
retrievable from Barbican and any attempt to
|
||||
retrieve decrypted data for that secret will fail.
|
||||
Defering the secret information to a PUT request
|
||||
Deferring the secret information to a PUT request
|
||||
is useful for secrets that are in binary format
|
||||
and are not suitable for base64 encoding.
|
||||
</wadl:doc>
|
||||
@@ -459,7 +459,7 @@ The following values are supported:</para>
|
||||
</response>
|
||||
<response status="404">
|
||||
<doc title="Error">This error code is returned when the
|
||||
supplied UUID doesn't match a order in the data store,
|
||||
supplied UUID doesn't match an order in the data store,
|
||||
which means the order doesn't exist. </doc>
|
||||
</response>
|
||||
</method>
|
||||
|
||||
Reference in New Issue
Block a user