From 18d5e8b9cc0b553ed03a4203bbfa6cdb0da6bf69 Mon Sep 17 00:00:00 2001
From: annegentle <anne@openstack.org>
Date: Fri, 20 Dec 2013 16:20:12 -0600
Subject: [PATCH] Removes paragraph saying UUID tokens are less secure
Change-Id: Ieb1fec05d6f7658e7cbb905285b66fcf024a175c
Closes-bug: 1253823
---
doc/security-guide/ch024_authentication.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/doc/security-guide/ch024_authentication.xml b/doc/security-guide/ch024_authentication.xml
index d78541b930..bb1a8d1c1f 100644
--- a/doc/security-guide/ch024_authentication.xml
+++ b/doc/security-guide/ch024_authentication.xml
@@ -102,7 +102,6 @@
<section xml:id="ch024_authentication-idp276176">
<title>Tokens</title>
<para>Once a user is authenticated, a token is generated and used internally in OpenStack for authorization and access. The default token <emphasis role="bold">lifespan</emphasis> is<emphasis role="bold"> 24 hours</emphasis>. It is recommended that this value be set lower but caution needs to be taken as some internal services will need sufficient time to complete their work. The cloud may not provide services if tokens expire too early. An example of this would be the time needed by the Compute Service to transfer a disk image onto the hypervisor for local caching.</para>
- <para>The Identity service could alternatively be configured to provide UUID tokens which are significantly shorter but may be less secure depending on your specific deployment model. Decisions about token implementation should take into consideration the level of trust needed within a given security domain.</para>
<para>Below is an example of a PKI token. Note that, in practice, the token id value is very long (e.g., around 3500 bytes), but for brevity we shorten it in this example.</para>
<screen>
"token": {