You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are various options in sssd.conf to handle missing or undefined shells, like e.g. override_shell, allowed_shells, vetoed_shells, shell_fallback and default_shell.
These options are mainly evaluated in get_shell_override() where currently only SYSDB_SHELL is taken into account but not OVERRIDE_PREFIX SYSDB_SHELL if it exists. It should be checked if a combination of the sssd.conf option together with the overridden shell will still lead to the expected reuslts.
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.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/2998
There are various options in sssd.conf to handle missing or undefined shells, like e.g. override_shell, allowed_shells, vetoed_shells, shell_fallback and default_shell.
These options are mainly evaluated in get_shell_override() where currently only SYSDB_SHELL is taken into account but not OVERRIDE_PREFIX SYSDB_SHELL if it exists. It should be checked if a combination of the sssd.conf option together with the overridden shell will still lead to the expected reuslts.
Comments
Comment from jhrozek at 2016-05-02 09:19:57
As discussed on Thursday, let's just keep this ticket in mind and in the bugtracker and defer for now.
milestone: NEEDS_TRIAGE => SSSD Deferred
Comment from jhrozek at 2016-05-26 10:09:39
Fields changed
rhbz: => 0
Comment from sbose at 2017-02-24 14:26:22
Metadata Update from @sbose:
Comment from pbrezina at 2020-03-24 14:16:44
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.
Comment from pbrezina at 2020-03-24 14:16:46
Metadata Update from @pbrezina:
The text was updated successfully, but these errors were encountered: