#697 Use command line arguments instead env vars for krb5_child
Closed: Fixed None Opened 8 years ago by sbose.

Currently we use env var to make the krb5_child aware of some global options. It would be more flexible if we change this to command line arguments.


Fields changed

type: defect => enhancement

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.6.0

Fields changed

coverity: =>
milestone: SSSD 1.6.0 => SSSD 1.7.0
upgrade: => 0

Fields changed

milestone: SSSD 1.8.0 => SSSD 1.9.0
patch: => 0

Fields changed

blockedby: =>
blocking: =>
milestone: SSSD 1.9.0 => SSSD Kerberos improvements
rhbz: =>

Fields changed

rhbz: => 0

Fields changed

feature_milestone: =>
proposed_priority: => Nice to have

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

milestone: SSSD Kerberos Improvements Feature => SSSD 1.10 beta

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

changelog: =>
design: =>
design_review: => 0
fedora_test_page: =>
milestone: SSSD 1.13 beta => NEEDS_TRIAGE
review: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12 beta

Fields changed

review: 0 => 1

If we need this, please bump back to a nearer milestone.

milestone: SSSD 1.12 beta => SSSD 1.13 beta

Fields changed

mark: => 0

Fields changed

milestone: SSSD 1.13 beta => SSSD 1.13 backlog
priority: minor => critical

Re-setting priority of 1.13 backlog tickets used for planning.

priority: critical => major

We've been talking about this enhancement for quite some time now, let's try in 1.14..

milestone: SSSD 1.13 backlog => SSSD 1.14 backlog
sensitive: => 0

Fields changed

patch: 0 => 1

Fields changed

milestone: SSSD 1.14 backlog => SSSD 1.15 Alpha
resolution: => fixed
status: new => closed

Metadata Update from @sbose:
- Issue assigned to sbose
- Issue set to the milestone: SSSD 1.15.0

2 years ago

Login to comment on this ticket.

Metadata