#1742 Allow different names for domains with local provider
Closed: Invalid None Opened 11 years ago by mzidek.

sss tools for local domains do not work with domains named other than LOCAL. Currently we have hardcoded name for local domains in function setup_db to "local" called by function init_sss_tools (used by all tools for local domains). It is case insensitive so it also allows name LOCAL (probably used by everyone and reason why we didn't noticed this bug).

We should allow different names as well.

Steps to reproduce:
1. configure domain with id_provider = local and name LOCAL2
2. use sss_useradd foo@LOCAL2 -> sss_useradd complains about no local domains configured


Fields changed

description: sss tools for local domains do not work with names other than LOCAL. Currently we have hardcoded name for local domains in function setup_db to "local" called by function init_sss_tools (used by all tools for local domains). It is case insensitive so it also allows name LOCAL (probably used by everyone and reason why didn't noticed this bug) etc.

We should allow different names as well.

Steps to reproduce:
1. configure domain with id_provider = local and name LOCAL2
2. use sss_useradd foo@LOCAL2 -> sss_useradd complains about no local domains configured => sss tools for local domains do not work with names other than LOCAL. Currently we have hardcoded name for local domains in function setup_db to "local" called by function init_sss_tools (used by all tools for local domains). It is case insensitive so it also allows name LOCAL (probably used by everyone and reason why didn't noticed this bug).

We should allow different names as well.

Steps to reproduce:
1. configure domain with id_provider = local and name LOCAL2
2. use sss_useradd foo@LOCAL2 -> sss_useradd complains about no local domains configured

Fields changed

description: sss tools for local domains do not work with names other than LOCAL. Currently we have hardcoded name for local domains in function setup_db to "local" called by function init_sss_tools (used by all tools for local domains). It is case insensitive so it also allows name LOCAL (probably used by everyone and reason why didn't noticed this bug).

We should allow different names as well.

Steps to reproduce:
1. configure domain with id_provider = local and name LOCAL2
2. use sss_useradd foo@LOCAL2 -> sss_useradd complains about no local domains configured => sss tools for local domains do not work domains named other than LOCAL. Currently we have hardcoded name for local domains in function setup_db to "local" called by function init_sss_tools (used by all tools for local domains). It is case insensitive so it also allows name LOCAL (probably used by everyone and reason why didn't noticed this bug).

We should allow different names as well.

Steps to reproduce:
1. configure domain with id_provider = local and name LOCAL2
2. use sss_useradd foo@LOCAL2 -> sss_useradd complains about no local domains configured

Fields changed

description: sss tools for local domains do not work domains named other than LOCAL. Currently we have hardcoded name for local domains in function setup_db to "local" called by function init_sss_tools (used by all tools for local domains). It is case insensitive so it also allows name LOCAL (probably used by everyone and reason why didn't noticed this bug).

We should allow different names as well.

Steps to reproduce:
1. configure domain with id_provider = local and name LOCAL2
2. use sss_useradd foo@LOCAL2 -> sss_useradd complains about no local domains configured => sss tools for local domains do not work with domains named other than LOCAL. Currently we have hardcoded name for local domains in function setup_db to "local" called by function init_sss_tools (used by all tools for local domains). It is case insensitive so it also allows name LOCAL (probably used by everyone and reason why didn't noticed this bug).

We should allow different names as well.

Steps to reproduce:
1. configure domain with id_provider = local and name LOCAL2
2. use sss_useradd foo@LOCAL2 -> sss_useradd complains about no local domains configured

Fields changed

description: sss tools for local domains do not work with domains named other than LOCAL. Currently we have hardcoded name for local domains in function setup_db to "local" called by function init_sss_tools (used by all tools for local domains). It is case insensitive so it also allows name LOCAL (probably used by everyone and reason why didn't noticed this bug).

We should allow different names as well.

Steps to reproduce:
1. configure domain with id_provider = local and name LOCAL2
2. use sss_useradd foo@LOCAL2 -> sss_useradd complains about no local domains configured => sss tools for local domains do not work with domains named other than LOCAL. Currently we have hardcoded name for local domains in function setup_db to "local" called by function init_sss_tools (used by all tools for local domains). It is case insensitive so it also allows name LOCAL (probably used by everyone and reason why we didn't noticed this bug).

We should allow different names as well.

Steps to reproduce:
1. configure domain with id_provider = local and name LOCAL2
2. use sss_useradd foo@LOCAL2 -> sss_useradd complains about no local domains configured

Fields changed

milestone: NEEDS_TRIAGE => SSSD Deferred

Fields changed

rhbz: => todo

suggest to close as local provider gets deprecated

changelog: =>
mark: => 0
review: => 1
sensitive: => 0

I agree with closing this ticket.

Since the local provider is not being developed anymore, I'm closing this ticket as wontfix.

resolution: => wontfix
status: new => closed

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

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

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