SSSD & POSIX attrs in GC
by Ondrej Valousek
Hi all,
Simple question:
In case we not use ldap_id_mapping, does SSSD require posix attrs in GC or not?
Thanks,
Ondrej
-----
The information contained in this e-mail and in any attachments is confidential and is designated solely for the attention of the intended recipient(s). If you are not an intended recipient, you must not use, disclose, copy, distribute or retain this e-mail or any part thereof. If you have received this e-mail in error, please notify the sender by return e-mail and delete all copies of this e-mail from your computer system(s). Please direct any additional queries to: communications(a)s3group.com. Thank You. Silicon and Software Systems Limited (S3 Group). Registered in Ireland no. 378073. Registered Office: South County Business Park, Leopardstown, Dublin 18.
7 years
Fwd: SSS sudoers and Ubuntu 16.04
by Clayton Daley
Good Morning,
We're doing some tests on Ubuntu 16.04 before upgrading and I'm having an
issue with sss (ldap) sudoers. On 14.04, everything works:
User clayton@<domain> may run the following commands on lin2:
> (root) ALL
> (root) NOPASSWD: /usr/bin/docker
On 16.04, the user has no problem authenticating, but:
User clayton@<domain> is not allowed to run sudo on lin3.
This is the same AD server and we use deployment automation code so I know
both systems are getting the same treatment. Here are the software
versions:
- ubuntu 14.04 vs 16.04
- sssd 1.11.8 vs 1.13.4
- sudo 1.8.9p5 vs. 1.8.19p2 << this is a manual upgrade of the 16.04
default in case a relevant bug was fixed
- realm 0.15.0-1 vs. 0.16.2.-2 << these appear to be the only versions
available through apt
- adcli 0.7.5-1 vs. adcli 0.8.1-1 << same apt limitation
Some additional notes and troubleshooting:
- Our AD server has an SSL certificate for the domain. ldapsearch has
been used to verify that it's functioning correctly. Based on logs, I'm
not clear if realm/sssd ever even uses the LDAPS port.
- "realm join" only works on Ubuntu 16.04 with either
"dns_canonicalize_hostname = false" (in krb5.conf) or
"--membership-software=samba". I've tested both of these options on
Ubuntu 14.04 and neither affect sudoers (i.e. it works fine).
- I've increased the debug_level and verified that sssd is loading both
the user's groups and sudoRoles (visually verified contents) and that sssd
is (correctly) resolving 2 rules that apply to the user when running sudo
-l:
[sudosrv_get_sudorules_from_cache] (0x0400): Returning 2 rules for
[clayton@<domain>]
Is there any more testing I should do at the sssd level or is this where
sssd hands off the data and sudo picks it up? Is there a specific line
that gives me more information on the handoff?
P.S. I'm also interested in resolving my "realm join" issue on 16.04. I've
done some digging on the (failing) adcli step of the failing realm join
command. The kinit works fine, but it chokes on "SASL(-1): generic
failure: GSSAPI Error: An invalid name was supplied (Success)". I've even
tried to complete the process passwordless (i.e. https://fedoraproject.
org/wiki/QA:Testcase_realmd_join_ccache) but I'm always prompted for a
password.
P.P.S. Is ldap_uri the right way to switch to LDAPS? Does it even work
with the ad provider?
Thanks,
Clayton Daley
7 years
