Bug 49393 – Synchronize simple authentication accounts to Samba

Bug 49393 - Synchronize simple authentication accounts to Samba


Summary:	Synchronize simple authentication accounts to Samba

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	S4 Connector
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:	Samba maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2019-04-29 18:31 CEST by Kevin Dominik Korte
Modified:	2024-06-27 12:10 CEST (History)
CC List:	3 users (show)

See Also:	45842
What kind of report is it?:	Feature Request
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?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2019080121000507
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 Kevin Dominik Korte

2019-04-29 18:31:01 CEST

Currently, there is no easy way to create simple authentication accounts in Samba4 from the UMC. However, that is regularly a requirement for software and hardware using AD as a backend. From Cisco VPN solutions to NetApp appliances, all these require user accounts in Samba4. Right now the only workaround is to create and change them using Windows tools or use full user accounts. It would be great if they could be created through the UMC.

Comment 1 Arvid Requate

2019-04-29 20:04:44 CEST

> Right now the only workaround is to create and change them

In what way? What are the desired settings and how do they differ from a "full user" account?

Comment 2 Jan-Luca Kiok

2024-06-27 12:10:10 CEST

This issue has been filed against UCS 4.4.

UCS 4.4 is out of general maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.