Learn more about these different git repos.
Other Git URLs
https://bugzilla.redhat.com/show_bug.cgi?id=828154 (Red Hat Enterprise Linux 6)
Description of problem: ipv6 address with square brackets doesn't work for krb5_server Version-Release number of selected component (if applicable): 1.8.0-32 How reproducible: Always Steps to Reproduce: 1. Set krb5_server = [2620:52:0:41c9:5054:ff:fe52:a3a6]:88 in sssd.conf 2. Perform a krb5 auth. Actual results: krb5 auth fails The log shows: (Mon Jun 4 16:23:37 2012) [sssd[be[LDAP-KRB5]]] [fo_resolve_service_done] (0x0020): Failed to resolve server '[2620:52:0:41c9:5054:ff:fe52:a3a6]': Domain name not found (Mon Jun 4 16:23:37 2012) [sssd[be[LDAP-KRB5]]] [set_server_common_status] (0x0100): Marking server '[2620:52:0:41c9:5054:ff:fe52:a3a6]' as 'not working' (Mon Jun 4 16:23:37 2012) [sssd[be[LDAP-KRB5]]] [be_resolve_server_done] (0x1000): Server resolution failed: 5 (Mon Jun 4 16:23:37 2012) [sssd[be[LDAP-KRB5]]] [be_mark_offline] (0x2000): Going offline! Expected results: auth should be successful. Additional info: krb5_server=2620:52:0:41c9:5054:ff:fe52:a3a6:88 seems to work.
Fields changed
blockedby: => blocking: => coverity: => feature_milestone: => keywords: => easyfix milestone: NEEDS_TRIAGE => SSSD 1.9.0 priority: major => minor tests: => 0 testsupdated: => 0 upgrade: => 0
owner: somebody => mzidek
b096321 fixed in master
milestone: SSSD 1.9.0 => SSSD 1.10.0 proposed_priority: => Undefined resolution: => fixed status: new => closed
patch: 0 => 1
milestone: SSSD 1.10.0 => SSSD 1.9.0 beta 7
Metadata Update from @jhrozek: - Issue assigned to mzidek - Issue set to the milestone: SSSD 1.9.0 beta 7
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/2407
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.