#1392 Incorrect message in krb5_child.log when krb5_fast_principal is unset
Closed: wontfix 4 years ago by pbrezina. Opened 11 years ago by sgallagh.

https://bugzilla.redhat.com/show_bug.cgi?id=831642 (Red Hat Enterprise Linux 6)

Description of problem:
Incorrect message in krb5_child.log when krb5_fast_principal is unset

Version-Release number of selected component (if applicable):
1.8.0-32

How reproducible:
Always

Steps to Reproduce:
1. Setup sssd with domain section as follows:
[domain/LDAP-KRB5]
debug_level=0xFFF0
id_provider = ldap
ldap_uri = ldap://ldapserver
ldap_search_base = dc=example,dc=com
auth_provider = krb5
krb5_server = krbserver
krb5_realm = EXAMPLE.COM
krb5_use_fast = demand
krb5_fast_principal =

2. The keytab /etc/krb5.keytab contains the principal
validprincipal@EXAMPLE.COM

3. Perform a krb5 auth for a valid user with correct password.

Actual results:
krb5 auth succeeds but krb5_child.log shows "Principal matched to the sample
((null)@EXAMPLE.COM)"

There is no principal as "((null)@EXAMPLE.COM)", hence the message in the log
looks incorrect.

Expected results:
Print appropriate message in the log when krb5_fast_principal is unset.

Additional info:

Fields changed

blockedby: =>
blocking: =>
coverity: =>
feature_milestone: =>
keywords: => easyfix
tests: => 0
testsupdated: => 0
upgrade: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12 beta

The issues is related to the input validation. Up until INI library provides this capability we can't do much.

Fields changed

proposed_priority: => Optional

This ticket has been evaluated for inclusion into SSSD 1.10 release and was decided to be excluded since it does not match the main goals and themes of the release. It might be considered for later releases.

Fields changed

milestone: SSSD 1.12 beta => SSSD 1.13 beta

Metadata Update from @sgallagh:
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

Metadata Update from @jhrozek:
- Custom field patch reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: easyfix

6 years ago

Metadata Update from @thalman:
- Custom field patch reset (from false)
- Custom field testsupdated reset (from false)
- Issue tagged with: Canditate to close

4 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 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/2434

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