Summary: | adcli not using fqdn | ||
---|---|---|---|
Product: | realmd | Reporter: | Marc H. Thoben <marc> |
Component: | adcli | Assignee: | Stef Walter <stefw> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | sbose |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Marc H. Thoben
2014-11-10 11:56:54 UTC
You can tell adcli about the FQDN (if it's not set as your host name) via the --host-fqdn option. See 'man adcli' Does that fix the problem for you? Yes, adcli with --host-fqdn manages to create the domain accounts with the proper attributes. But of course, no configuration files for sssd are created then. Only "realm join" does that. And "realm" has no such feature yet to call adcli with --host-fqdn. As a workaround I do the following: 1) realm join --verbose --client-software=sssd --server-software=active-directory --membership-software=adcli --user-principal=host/ahtest1.mpipz.mpg.de@MPIPZ.MPG.DE -U mthoben_local mpipz.mpg.de 2) adcli delete-computer --verbose --domain mpipz.mpg.de --domain-realm MPIPZ.MPG.DE --domain-controller 10.1.0.224 --login-user mthoben_local --prompt-password ahtest1.mpipz.mpg.de 3) adcli join --verbose --domain mpipz.mpg.de --domain-realm MPIPZ.MPG.DE --domain-controller 10.1.0.224 --host-fqdn=ahtest1.mpipz.mpg.de --user-principal=host/ahtest1.mpipz.mpg.de@MPIPZ.MPG.DE --login-type user --login-user mthoben_local --prompt-password 4) systemctl restart sssd.service Thanks for your help. Hi Stef, do you think anything needs to be done for this ticket? I can see the following options: - do nothing, just close the ticket - realm just fails if gethostname() returns a short name and asks to set the FQDN - realm gets a new option for the FQDN - realm adds the domain name of the domain to join if gethostname() returns a short name - a combination of the above options Do you have a preference? bye, Sumit (In reply to Sumit Bose from comment #3) > Hi Stef, > > do you think anything needs to be done for this ticket? I can see the > following options: > > - do nothing, just close the ticket > - realm just fails if gethostname() returns a short name and asks to set the > FQDN > - realm gets a new option for the FQDN This probably makes sense. > - realm adds the domain name of the domain to join if gethostname() returns > a short name I like this one. Would it actually work? But according to the description, it also seems like there's a bug in adcli where it registers duplicate servicePrincipalName entries (and keytab entries) when it thinks the netbios name and fqdn are identical. Hi! I still (2018) encounter the same problem. In CentOS versions 7.7, RHEL 7.4, Ubuntu 16.04 and Ubuntu 18.04. This problem also affects SSO. While the keytab is not recreated, SSO (ssh) can not be done. When trying to ssh using the kerberos ticket and in verbose mode (ssh -vvv -K hostname) I get the message below: "server not found in kerberos database" Thanks, Marcelo Módolo -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/realmd/adcli/issues/1. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.