Comment 1 Felix Botner 2013-08-06 15:45:51 CEST

Workaround: UDM search


-> udm users/user list --filter oxAccessUSM=OK| grep '^DN'
DN: uid=test2,cn=users,dc=fff,dc=ggg

-> udm users/user list --filter oxAccessUSM=Not| grep '^DN'
DN: uid=test1,cn=users,dc=fff,dc=ggg

Comment 2 Alexander Kläser 2013-09-11 14:24:25 CEST

*** Bug 32473 has been marked as a duplicate of this bug. ***

Comment 3 Alexander Kläser 2014-02-28 19:28:31 CET

*** Bug 34204 has been marked as a duplicate of this bug. ***

Comment 4 Alexander Kläser 2014-04-24 11:35:41 CEST

*** Bug 34494 has been marked as a duplicate of this bug. ***

Comment 5 Janis Meybohm 2014-07-25 13:09:09 CEST

Ticket#: 2014072421000332

Reported again in form of "search filter for locked accounts does not work"


Maybe we should just disable the options that do not work for now?

Comment 6 Janis Meybohm 2014-07-25 13:17:49 CEST

For account locking/locked login, even the udm cli filter does not seem to work correctly:

root@master:~# udm users/user list | grep locked -c
16
root@master:~# udm users/user list --filter locked=none | grep ^DN -c
14
root@master:~# udm users/user list --filter locked=all | grep ^DN -c
2
root@master:~# udm users/user list --filter locked=windows | grep ^DN -c
2
root@master:~# udm users/user list --filter locked=posix | grep ^DN -c
0
root@master:~# udm users/user list | grep locked
  locked: none
  locked: none
  locked: none
  locked: none
  locked: none
  locked: none
  locked: posix
  locked: none
  locked: none
  locked: none
  locked: windows
  locked: none
  locked: none
  locked: none
  locked: none
  locked: all

Comment 7 Jannik Ahlers 2018-07-17 09:56:42 CEST

*** Bug 47211 has been marked as a duplicate of this bug. ***

Comment 8 Jannik Ahlers 2018-07-17 10:28:59 CEST

The problem is that the search function right now only searches for the values 'true' and 'false', while the backend stores the values according to the udm syntaxes:
(
 'OkOrNot':     'OK'   - 'Not'
 'TrueFalseUp': 'TRUE' - 'FALSE'
 'boolean':     '1'    - '0'
)
There is a fix for this in branch jahlers/32167-udm-search-boolean which simply replaces the checkboxes in udm search with dropdown menues.
Unfortunately this doesn't work for the boolean syntax due to bug #47364.

Comment 9 Florian Best 2018-07-17 12:37:04 CEST

I send a pull request which enhances this handling. I think it can easily be adapted so that all checkbox-syntax-class values are correctly mapped (instead of adding a not so nice drop down menu).

Comment 10 Johannes Keiser 2018-08-27 15:08:53 CEST

(In reply to Florian Best from comment #9)
> I send a pull request which enhances this handling. I think it can easily be
> adapted so that all checkbox-syntax-class values are correctly mapped
> (instead of adding a not so nice drop down menu).

The pull request has been implemented with Bug #40672.
It has been adapted with commit 31f894ee7e658948d4b042ba144c6ff11f83a422
to include all boolean syntax classes.

Comment 11 Dirk Wiesenthal 2018-08-29 03:12:53 CEST

So... this is more a duplicate of Bug#40672? Because I cannot see any changes made for this bug nor do I see something in the YAML files.

It seems as if any change related to this bug was reverted with the bug mentioned above.

Comment 12 Stefan Gohmann 2018-09-18 07:54:44 CEST

I think the target milestone is wrong. Can you check this?

Comment 13 Johannes Keiser 2018-09-20 10:01:12 CEST

(In reply to Florian Best from comment #9)
> I send a pull request which enhances this handling. I think it can easily be
> adapted so that all checkbox-syntax-class values are correctly mapped
> (instead of adding a not so nice drop down menu).

The pull request has been implemented with Bug #40672.
It has been adapted with commit 1587325369a81ae311ef195e054d1c4907b62815
to include all boolean syntax classes.

Comment 14 Dirk Wiesenthal 2018-10-04 10:04:04 CEST

Duplicate of Bug#40672

*** This bug has been marked as a duplicate of bug 40672 ***