Blame SOURCES/0002-doc-explain-that-all-credential-cache-types-are-supp.patch

ee944e
From 7e71dd109601d3be09cdda37cd4bf99ba867ce19 Mon Sep 17 00:00:00 2001
ee944e
From: Sumit Bose <sbose@redhat.com>
ee944e
Date: Wed, 1 Nov 2017 12:01:18 +0100
ee944e
Subject: [PATCH 2/4] doc: explain that all credential cache types are
ee944e
 supported
ee944e
ee944e
---
ee944e
 doc/adcli.xml | 12 ++++++++----
ee944e
 1 file changed, 8 insertions(+), 4 deletions(-)
ee944e
ee944e
diff --git a/doc/adcli.xml b/doc/adcli.xml
ee944e
index e18ba5d..c54cc1b 100644
ee944e
--- a/doc/adcli.xml
ee944e
+++ b/doc/adcli.xml
ee944e
@@ -118,11 +118,15 @@
ee944e
 			is automatically discovered.</para></listitem>
ee944e
 		</varlistentry>
ee944e
 		<varlistentry>
ee944e
-			<term><option>-C, --login-ccache=<parameter>/path/to/file</parameter></option></term>
ee944e
+			<term><option>-C, --login-ccache=<parameter>ccache_name</parameter></option></term>
ee944e
 			<listitem><para>Use the specified kerberos credential
ee944e
-			cache to authenticate with the domain. If no file is specified or
ee944e
-			<option>-C</option> is used, then the default kerberos credential cache will
ee944e
-			be used.</para></listitem>
ee944e
+                        cache to authenticate with the domain. If no credential
ee944e
+                        cache is specified, the default kerberos credential
ee944e
+                        cache will be used. Credential caches of type FILE can
ee944e
+                        be given with the path to the file. For other
ee944e
+                        credential cache types, e.g. DIR, KEYRING or KCM, the
ee944e
+                        type must be specified explicitly together with a
ee944e
+                        suitable identifier.</para></listitem>
ee944e
 		</varlistentry>
ee944e
 		<varlistentry>
ee944e
 			<term><option>-U, --login-user=<parameter>User</parameter></option></term>
ee944e
-- 
ee944e
2.13.6
ee944e