#37 DSGW can't change "userpassword" and "sambantpassword" fields synchronously
Closed: wontfix 2 years ago by mreynolds. Opened 9 years ago by mkosek.

https://bugzilla.redhat.com/show_bug.cgi?id=726282

Description of actual problem:

When Samba uses ldapsam backend it may be necessary to change "userpassword"
and "sambantpassword" fields synchronously. But password changing in DSGW
changes only "userpassword" field in Directory Server.

To allow this feature I've changed 2 files in the source code of DSGW:
1. I've added this definition to dsgw.h:
      #define DSGW_ATTRTYPE_SAMBANTPASSWORD   "sambaNTPassword"
2. I've changed domodify.c. Please look at the attachment.

DSGW with these modifications was tested and worked fine for Red Hat Directory
Server 8.1.0-1 and Samba 3.0.33.

If this way of solving the problem is acceptable, it might be better to build
this new feature in DSGW with more flex (allow switch it off and on through the
configuration file).

Additional info:
The modification of domodify.c is based on the code of mkntpwd tool (the work
of Anton Roeckseisen anton@genua.de) and also contains md4.c source from Samba
source code.

batch update to FUTURE milestone

set default ticket origin to Community

Added initial screened field value.

Metadata Update from @rmeggins:
- Issue set to the milestone: 389-dsgw FUTURE

4 years ago

DSGW is deprecated, closing ticket...

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None (was: Needs Review)
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

2 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/37

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