URL:
https://github.com/SSSD/sssd/pull/630
Title: #630: KCM/SECRETS: Use a library to access the secrets storage instead of the
secrets responder, deprecate secrets responder
jhrozek commented:
"""
Thank you, I merged your patch. I also changed the patch that fixes to libsecrets by
default, this is the diff:
```
diff --git a/src/man/sssd-kcm.8.xml b/src/man/sssd-kcm.8.xml
index 78d3551d4..ec27aa57b 100644
--- a/src/man/sssd-kcm.8.xml
+++ b/src/man/sssd-kcm.8.xml
@@ -121,17 +121,9 @@ systemctl enable sssd-kcm.socket
<refsect1 id='storage'>
<title>THE CREDENTIAL CACHE STORAGE</title>
<para>
- The credential caches are stored in the SSSD secrets service (see
- <citerefentry>
-
<refentrytitle>sssd-secrets</refentrytitle><manvolnum>5</manvolnum>
- </citerefentry>
- for more details). Therefore it is important that also the sssd-secrets
- service is enabled and its socket is started:
- <programlisting>
-systemctl start sssd-secrets.socket
-systemctl enable sssd-secrets.socket
- </programlisting>
- Your distribution should already set the dependencies between the services.
+ The credential caches are stored in a database, much like SSSD
+ caches user or group entries. The database is typically
+ located at <quote>/var/lib/sss/secrets</quote>.
</para>
</refsect1>
```
"""
See the full comment at
https://github.com/SSSD/sssd/pull/630#issuecomment-412364601