On Fri, Jun 03, 2016 at 05:55:24PM +0200, Lukas Slebodnik wrote:
On (03/06/16 09:07), Stephen Gallagher wrote:
>On 05/13/2016 10:29 AM, Lukas Slebodnik wrote:
>> On (11/05/16 17:35), Lukas Slebodnik wrote:
>>> On (10/05/16 17:06), Jakub Hrozek wrote:
>>>> On Tue, May 10, 2016 at 09:51:18AM -0400, Stephen Gallagher wrote:
>>>>> On 05/10/2016 09:45 AM, Jakub Hrozek wrote:
><snip>
>>> This basic sssd configuration expects that proxy provider will
>>> be installed by default. And that's not reality.
>>>
>>> It's only installed with meta-package sssd.
>>> But It will not work with minimal installation of sssd.
>>> "yum install -y sssd-ldap"
>>> or even just "sssd-common"
>>>
>>> If should start without failures and with default configuration
>>> then we should change pacakging as well and recommend similar packaging
change
>>> to other downstreams (debian, opensuse ...)
>
>
>Sorry it took me so long to reply on this. I should have examined this more
>closely. It was probably a bad idea to have the proxy provided be the default
It wasn't a bad idea per se.
I realized this issue later when I ran downstream tests and noticed AVCs.
Yeah, sorry, I didn't realize this either because I build from source
during my review :-/
>setup, since it might or might not be installed (and we probably don't want to
>force its inclusion). I guess it would make more sense for the native
'local'
>provider to be the default.
>
maybe.
FWIW, I already started on the 'files' provider and have some WIP
patches in my branches, but I don't think I will finish them before we
release 1.14 (~3 weeks), so I would also vote to include a provider that
already exists for the time being and switch to the files provider in
the next 1.14 release.