#1688 sssd_sudo prints wrong debug message when notBefore or notAfter attribute is missing
Closed: Fixed None Opened 7 years ago by pbrezina.

If sudo_timed = true and notBefore or notAfter attribute is missing, sssd_sudo always prints

(Tue Dec  4 14:22:44 2012) [sssd[sudo]] [sysdb_sudo_check_time] (0x1000): notBefore attribute is missing, the rule [<missing>] is valid

instead of replacing <missing> with rule name.


Fields changed

description: It always prints

{{{
(Tue Dec 4 14:22:44 2012) [sssd[sudo]] [sysdb_sudo_check_time] (0x1000): notBefore attribute is missing, the rule [<missing>] is valid
}}}

instead of replacing <missing> with rule name.
=> If sudo_timed = true and notBefore or notAfter attribute is missing, sssd_sudo always prints

{{{
(Tue Dec 4 14:22:44 2012) [sssd[sudo]] [sysdb_sudo_check_time] (0x1000): notBefore attribute is missing, the rule [<missing>] is valid
}}}

instead of replacing <missing> with rule name.

milestone: NEEDS_TRIAGE => SSSD 1.9.3
resolution: => fixed
status: new => closed

This is a devel task. Nothing to verify in RHEL.

rhbz: => 0

Metadata Update from @pbrezina:
- Issue assigned to pbrezina
- Issue set to the milestone: SSSD 1.9.3

3 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/2730

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