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

Exclude some more openldap attributes during migration #5734

Closed
Firstyear opened this issue Apr 20, 2023 · 0 comments · Fixed by #5735
Closed

Exclude some more openldap attributes during migration #5734

Firstyear opened this issue Apr 20, 2023 · 0 comments · Fixed by #5735
Labels
needs triage The issue will be triaged during scrum

Comments

@Firstyear
Copy link
Contributor

A customer reported an issue with openldap to 389ds migration. This was due to their openldap instance using a number of openldap attributes that I had not encountered in other migrations.

These attributes are operational to openldap only and can be safely excluded.

@Firstyear Firstyear added the needs triage The issue will be triaged during scrum label Apr 20, 2023
Firstyear added a commit to Firstyear/389-ds-base that referenced this issue Apr 20, 2023
Bug Description: A customer reported an issue with openldap to 389ds migration. This was due to
their openldap instance using a number of openldap attributes that I had not encountered in other
migrations.

These attributes are operational to openldap only and can be safely excluded.

Fix Description: Exclude pwdFailureTime and ContextCSN

fixes: 389ds#5734

Author: William Brown <william@blackhats.net.au>

Review by: ???
Firstyear added a commit that referenced this issue Apr 21, 2023
Bug Description: A customer reported an issue with openldap to 389ds migration. This was due to
their openldap instance using a number of openldap attributes that I had not encountered in other
migrations.

These attributes are operational to openldap only and can be safely excluded.

Fix Description: Exclude pwdFailureTime and ContextCSN

fixes: #5734

Author: William Brown <william@blackhats.net.au>

Review by: ???
Firstyear added a commit that referenced this issue Apr 21, 2023
Bug Description: A customer reported an issue with openldap to 389ds migration. This was due to
their openldap instance using a number of openldap attributes that I had not encountered in other
migrations.

These attributes are operational to openldap only and can be safely excluded.

Fix Description: Exclude pwdFailureTime and ContextCSN

fixes: #5734

Author: William Brown <william@blackhats.net.au>

Review by: ???
Firstyear added a commit that referenced this issue Apr 21, 2023
Bug Description: A customer reported an issue with openldap to 389ds migration. This was due to
their openldap instance using a number of openldap attributes that I had not encountered in other
migrations.

These attributes are operational to openldap only and can be safely excluded.

Fix Description: Exclude pwdFailureTime and ContextCSN

fixes: #5734

Author: William Brown <william@blackhats.net.au>

Review by: ???
Firstyear added a commit that referenced this issue Apr 21, 2023
Bug Description: A customer reported an issue with openldap to 389ds migration. This was due to
their openldap instance using a number of openldap attributes that I had not encountered in other
migrations.

These attributes are operational to openldap only and can be safely excluded.

Fix Description: Exclude pwdFailureTime and ContextCSN

fixes: #5734

Author: William Brown <william@blackhats.net.au>

Review by: ???
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage The issue will be triaged during scrum
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant