#1444 ad_server = <IP Address> doesn't work.
Closed: Invalid None Opened 11 years ago by kaushikub.

Domain section of sssd.conf:

[domain/ADTEST]
debug_level = 0xFFF0
id_provider = ad
ad_server = <IP>
ad_domain = sssdad.com
krb5_canonicalize = False

Looking up user fails. Logs show the following failures:

(Fri Jul 27 18:27:44 2012) [sssd[be[ADTEST]]] [sasl_bind_send] (0x0020): ldap_sasl_bind failed (-2)[Local error]
(Fri Jul 27 18:27:44 2012) [sssd[be[ADTEST]]] [sasl_bind_send] (0x0080): Extended failure message: [SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure.  Minor code may provide more information (Cannot determine realm for numeric host address)]

This happens if you cannot resolve IP -> A name, do you have PTR records for the AD server in DNS ?

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.10.0

Fields changed

proposed_priority: => Nice to have

Cleaning the 1.10 milestones before putting tickets into it.

milestone: SSSD 1.10.0 => Temp milestone

Moving planned features and bug fixes into the 1.10 bucket.

milestone: Temp milestone => SSSD 1.10.0

Fields changed

milestone: SSSD 1.10.0 => Temp milestone

Moving all the features planned for 1.10 release into 1.10 beta.

milestone: Temp milestone => SSSD 1.10 beta

Fields changed

priority: major => minor

Fields changed

selected: => Not need

Moving tickets that are not a priority for SSSD 1.10 into the next release.

milestone: SSSD 1.10 beta => SSSD 1.11 beta

Fields changed

mark: => 0

This is not supposed to work, sorry.

changelog: =>
design: =>
design_review: => 0
fedora_test_page: =>
resolution: => wontfix
review: => 0
status: new => closed

Metadata Update from @kaushikub:
- Issue set to the milestone: SSSD 1.13.1

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2486

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata