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

No error returned when adding an entry matching filters for a non existing automember group #3967

Closed
389-ds-bot opened this issue Sep 13, 2020 · 6 comments
Labels
closed: fixed Migration flag - Issue
Milestone

Comments

@389-ds-bot
Copy link

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


Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1759142

Description of problem:
When creating an entry with attributes matching the automemberFilter of an auto
membership definition, but for which the autoMemberDefaultGroup doesn't exist,
the entry is created successfully, without any error or even without warning

Version-Release number of selected component (if applicable):
389-ds-base-1.3.9.1-10.el7.x86_64
and 389-ds-base-1.3.10.1-2.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. enable the memberof plugin
2. Add a configuration entry for the auto Membership Plugin,
autoMemberDefaultGroup value being a non existing group. For example :
dn: cn=test users,cn=Auto Membership Plugin,cn=plugins,cn=config
objectclass: autoMemberDefinition
autoMemberScope: ou=People,dc=example,dc=com
autoMemberFilter: objectclass=nsView
autoMemberDefaultGroup: cn=invalid group,ou=Groups,dc=example,dc=com
autoMemberGroupingAttr: uniqueMember:dn

cn=invalid group,ou=Groups,dc=example,dc=com does not exist

3. create en entry part of the autoMemberScope of the auto Membership plugin
definition, having an attribute matching the autoMemberFilter. For example :
dn: ou=test view,ou=People,dc=example,dc=com
objectClass: top
objectClass: organizationalUnit
objectClass: nsView
ou: test view
description: test view

Actual results:
The entry is added successfully

Expected results:
The operation should be rejected, or at least an error message should be
returned/logged to warn that the group to which the entry should be added does
not exist.


Additional info:
linked to https://pagure.io/389-ds-base/issue/50077 ??
@389-ds-bot 389-ds-bot added the closed: fixed Migration flag - Issue label Sep 13, 2020
@389-ds-bot 389-ds-bot added this to the 1.3.10 milestone Sep 13, 2020
@389-ds-bot
Copy link
Author

Comment from tbordaz (@tbordaz) at 2020-02-26 14:29:47

Metadata Update from @tbordaz:

@389-ds-bot
Copy link
Author

Comment from tbordaz (@tbordaz) at 2020-02-26 14:32:16

Metadata Update from @tbordaz:

  • Issue assigned to tbordaz

@389-ds-bot
Copy link
Author

Comment from tbordaz (@tbordaz) at 2020-02-26 14:33:15

Metadata Update from @tbordaz:

  • Custom field origin adjusted to None
  • Custom field reviewstatus adjusted to None
  • Issue set to the milestone: 1.3.10 (was: 0.0 NEEDS_TRIAGE)

@389-ds-bot
Copy link
Author

389-ds-bot commented Sep 13, 2020

Comment from tbordaz (@tbordaz) at 2020-02-26 18:24:54

#3968

@389-ds-bot
Copy link
Author

Comment from tbordaz (@tbordaz) at 2020-02-27 15:54:20

60ae321..c809642 master (1.4.3)
59e3a4a..2b54404 389-ds-base-1.4.2
074dac5..3d8522b 389-ds-base-1.4.1
4ae4468..a587d4b 389-ds-base-1.3.10

@389-ds-bot
Copy link
Author

Comment from tbordaz (@tbordaz) at 2020-02-27 15:54:31

Metadata Update from @tbordaz:

  • Issue close_status updated to: fixed
  • 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: fixed Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant