Bug 38241 – UCS as a member of an Active Directory domain; Incomplete steps on how to enable password service

Bug 38241 - UCS as a member of an Active Directory domain; Incomplete steps on how to enable password service


Summary:	UCS as a member of an Active Directory domain; Incomplete steps on how to ena...

Status:	RESOLVED WONTFIX

Product:	UCS manual
Classification:	Unclassified
Component:	Domain services / LDAP
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.1-x
Assigned To:	Docu maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-04-13 11:32 CEST by Janis Meybohm
Modified:	2024-04-17 13:16 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	---
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
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Janis Meybohm

2015-04-13 11:32:20 CEST

The description on how to enable the password service is missing the actual step to make the ad-connector write the password into LDAP:

# ucr unset connector/ad/mapping/user/password/kinit

Comment 1 Janis Meybohm

2015-04-13 14:36:42 CEST

It is also necessary to re-initialize the AD connector of cause (<http://sdb.univention.de/1322>).  Though moving the internal-database should be good enough as member mode implies AD connector in read mode.

Comment 2 Janis Meybohm

2015-06-02 12:01:08 CEST

http://sdb.univention.de/1332 now contains all necessary steps (part from manual + missing parts)

Comment 3 Nico Gulden

2024-04-17 13:16:34 CEST

This bug hasn't seen any update for several years. I close it.

If you still see a need for it, you can reopen the bug. Please add an argumentation about why it's important to take care of it.