Bug 31789 - Defining additional nsswitch.conf entries.
Defining additional nsswitch.conf entries.
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: PAM
UNSTABLE
Other Linux
: P5 normal with 2 votes (vote)
: UCS 3.x
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-21 11:43 CEST by Janek Walkenhorst
Modified: 2020-07-02 16:20 CEST (History)
4 users (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Janek Walkenhorst univentionstaff 2013-06-21 11:43:13 CEST
Currently univention-pam has an UCR template for /etc/nsswitch.conf; Thus it is not possible for other packages to add "their" entries to the nsswitch.conf.

Is should either be a multifile UCR template or the UCR template should allow generic additions via UCRV.
Comment 1 Ingo Sieverdingbeck univentionstaff 2018-05-16 16:16:05 CEST
Defining additional nsswitch.conf entries would be helpful for the sudo-ldap cool solution to get rid of the univention-pam fork.
Comment 2 Stefan Gohmann univentionstaff 2019-01-03 07:30:41 CET
This issue has been filed against the UCS version "unstable" which does not really exist. Please change the version value.
Comment 3 Ingo Steuwer univentionstaff 2020-07-02 16:20:33 CEST
I close this Bugzilla entry as they are filed without a valid UCS version and haven't been changed for more than a year.

In case the bug or feature request is still valid please re-open with the valid UCS version and an updated description.