#62 FleetCommander: Explain better the perms of the created dirs
Merged 6 years ago by jhrozek. Opened 6 years ago by fidencio.

@@ -97,6 +97,33 @@ 

  ``/var/lib/sss/deskprofile/<domain>/<username>/<profilename>.json``.

  The ``<username>`` directories need to be owned by the user being logged in.

  

+ The structure of the the created dirs follow::

+ 

+     /var/lib/sss/deskprofile/<domain>/<username>/<profilename>.json

+                 ------------ -------- ---------- ------------------

+                      |          |          |            |

+                      v          |          |            |

+     Created by sssd package as  |          |            |

+     root:root (or sssd:sssd)    |          |            |

+     and has permissions 0751    |          |            |

+                                 |          |            |

+                                 v          |            |

+                 Owned by user:user_group   |            |

+                 and has permissions 0751   |            |

+                                            |            |

+                                            |            |

+                                            v            |

+                         Owned by user:user_group        |

+                         and has permissions 0700        |

+                                                         |

+                                                         v

+                                         Owned by user:user_group

+                                         and has permissions 0400

+ 

+ Please, keep in mind that this feature relies on CAP_SETUID and

+ CAP_SETGID to properly work as expected and relies on SSSD being run

+ as privileged user (root).

+ 

  The ``<profilename.json>`` file must include the priority as a number

  which is read from the rule's ``prio`` attribute. The Fleet Commander

  client component will then process the JSON files in this priority. The

This commit has the intented to explain better the perms of the dirs
that have to be created by SSSD when taking advantage of FleetCommander
integration and also explicitly says that we depend on CAP_SETUID and
CAP_SETGID.

Signed-off-by: Fabiano Fidêncio fidencio@redhat.com

rebased onto 9ed506d2d123cf8d875c3218b8f4c62d919fc84e

6 years ago

rebased onto d501097bd3edca46c31d434b6f77a26c73bda47f

6 years ago

Patch has been updated reflecting what has been merged.
May I have it merged in case anyone picks it up in a week or so?

rebased onto 186276c

6 years ago

Pull-Request has been merged by jhrozek

6 years ago
Metadata