#3139 secrets: Consider if proxy provider globally is allowed
Closed: wontfix 4 years ago by pbrezina. Opened 7 years ago by jhrozek.

Right now, setting the proxy provider in the global secrets section doesn't read the proxy-specific settings from the global secrets section. One must set up the per-UID routing for that to work correctly.

We need to either fix that, or, if we decide that proxy provider is valid only for per-user namespaces, warn the user in a nice way


Fields changed

milestone: NEEDS_TRIAGE => SSSD Deferred

ticket #2243 tracks a more generic solution.

resolution: => wontfix
status: new => closed

Fields changed

resolution: wontfix =>
status: closed => reopened

sorry about closing, wrong ticket

Just so that I don't forget:

}}}diff --git a/src/responder/secrets/providers.c b/src/responder/secrets/providers.c
index 4c60198..8b8106f 100644
--- a/src/responder/secrets/providers.c
+++ b/src/responder/secrets/providers.c
@@ -112,6 +112,7 @@ int sec_req_routing(TALLOC_CTX *mem_ctx, struct sec_req_ctx *secreq,
     }

     if (!secreq->base_path) secreq->base_path = SEC_BASEPATH;
+    if (!secreq->cfg_section) secreq->cfg_section = CONFDB_SEC_CONF_ENTRY;

     ret = sec_get_provider(sctx, provider, handle);
     if (ret == ENOENT) {

Fields changed

cc: => cheimes@redhat.com

Fields changed

rhbz: => todo

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Patches welcome

7 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/4172

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