#1104 pwpolicy-mod doesn't accept old attribute values
Closed: Fixed None Opened 13 years ago by edewata.

The pwpolicy-mod operation fails if one of the parameters contains an old value.

Add the following policy:

# ipa pwpolicy-add testgroup --priority=1 --maxlife=30
  Group: testgroup
  Max lifetime (days): 30
  Priority: 1

Modifying the priority while keeping the old max life fails:

# ipa pwpolicy-mod testgroup --priority=5 --maxlife=30
ipa: ERROR: no modifications to be performed

Modifying the max life while keeping the old priority fails:

# ipa pwpolicy-mod testgroup --priority=1 --maxlife=60
ipa: ERROR: invalid 'priority': priority must be a unique value (1 already used by
testgroup)

If each parameter is changed separately (without specifying old values) it will work just fine.

This is a problem for the UI because currently when the UI performs an update operation it always sends all values back to the server regardless whether they are changed or not.

The solution is either to fix the server to accept old values, or to fix the UI to send only dirty fields, or both.


I will do this one along with #1103 - I have already a patch for that one.

Metadata Update from @edewata:
- Issue assigned to mkosek
- Issue set to the milestone: FreeIPA 2.1 - 2011/08 (Final)

7 years ago

Login to comment on this ticket.

Metadata