Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

documentation: migrate_password.pl must be modified #143

Closed
389-ds-bot opened this issue Sep 12, 2020 · 8 comments
Closed

documentation: migrate_password.pl must be modified #143

389-ds-bot opened this issue Sep 12, 2020 · 8 comments
Labels
closed: won't fix Migration flag - Issue
Milestone

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/143


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

Description of problem:

When doing a basic install of Samba and FDS and following the Howto for
integrating the two the migrate_password.pl must be modified to migrate the
Samba Administrator account.

The following items must be commented out of migrate_password.pl:

    * mailRoutingAddress
    * mailHost
    * inetLocalMailRecipient
    * kerberosSecurityObject
    * krbName

A note that these items need to be commented out, or at least the some editing
of the migrate_password.pl file may be necessary, would be helpful.

Version-Release number of selected component (if applicable):
FDS 1.0.1
Samba 3.0.10
Migration Tools from http://www.padl.com/download/ v47

How reproducible:

Always

Steps to Reproduce:
1. Create file with contents:
    Administrator:x:0:0:Samba Admin:/root:/bin/bash
2. /usr/share/openldap/migration/migrate_passwd.pl /tmp/sambaAdmin >
/tmp/sambaAdmin.ldif
3. /opt/fedora-ds/slapd-<server>/ldif2ldap "cn=Directory manager" password
/tmp/sambaAdmin.ldif

Actual results:

The first error is about kerberosSecurityObject being an unknown objectClass.
Similar errors are given about the other items listed above.

The user is not added to FDS.

Expected results:

The user should be added to FDS

Additional info:
@389-ds-bot 389-ds-bot added the closed: won't fix Migration flag - Issue label Sep 12, 2020
@389-ds-bot 389-ds-bot added this to the FUTURE milestone Sep 12, 2020
@389-ds-bot
Copy link
Author

Comment from rmeggins (@richm) at 2012-01-10 06:12:03

batch update moving tickets to future

@389-ds-bot
Copy link
Author

Comment from rmeggins (@richm) at 2012-08-14 19:56:22

set default ticket origin to Community

@389-ds-bot
Copy link
Author

Comment from nkinder (@nkinder) at 2012-08-28 04:14:31

Added initial screened field value.

@389-ds-bot
Copy link
Author

@389-ds-bot
Copy link
Author

Comment from nkinder (@nkinder) at 2017-02-11 23:05:42

Metadata Update from @nkinder:

  • Issue set to the milestone: FUTURE

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-04-05 07:36:43

Is this issue still relevant?

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-04-05 07:36:49

Metadata Update from @Firstyear:

  • Custom field reviewstatus adjusted to new (was: Needs Review)
  • Issue close_status updated to: None

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2019-08-23 22:14:49

Metadata Update from @mreynolds389:

  • Custom field reviewstatus adjusted to None (was: new)
  • Issue close_status updated to: wontfix
  • Issue status updated to: Closed (was: Open)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: won't fix Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant