Correction they are full AD objects. So any ideas for a workaround are welcome.
-Erinn
___
sssd-users mailing list -- sssd-users@lists.fedorahosted.org
To unsubscribe send an email to sssd-users-le...@lists.fedorahosted.org
Fedora Code of Conduct:
https
So yes I saw krb5_map_user, problem is we have hundreds of these users and that
list grows and shrinks dynamically as people come and go. I could do some
really terrible hack to pull the data from wherever and stick it into
krb5_map_user but that's just awful. Ultimately regex support here would
On Thu, Oct 24, 2019 at 11:52:56AM +0200, Pavel Březina wrote:
> On 10/23/19 11:31 PM, Erinn Looney-Triggs wrote:
> > Folks I am in the process of working through this but I thought I would
> > throw it out just in case there were other thoughts or I was chasing
> > down the wrong lane.
> >
> > We
On 10/23/19 11:31 PM, Erinn Looney-Triggs wrote:
Folks I am in the process of working through this but I thought I would
throw it out just in case there were other thoughts or I was chasing
down the wrong lane.
We have a requirement for sudo to use a different password than the user
password
On 10/24/19 6:32 AM, Spike White wrote:
sssd experts,
I think this is proper and expected sssd behavior. Since I'm using
short names for all lookups, that is called a "domain-less search".
Yes, if you are using short names the domain_resolution_order is required.
Look at https://docs.pa
