Skip to content
  1. Feb 22, 2021
    • Varun Mylaraiah's avatar
      Merge pull request #511 from t-woerner/ipaclient_otp_rmkeytab_error#7 · 3c666ccd
      Varun Mylaraiah authored
      ipaclient: Do not fail on rmkeytab error #7
      v0.3.5
      3c666ccd
    • Thomas Woerner's avatar
      ipaclient: Do not fail on rmkeytab error #7 · 976cd1ba
      Thomas Woerner authored
      Due to commit f3f9672d527008dc741ac90aa465bac842eea08d (ipa-rmkeytab: Check
      return value of krb5_kt_(start|end)_seq_get) in IPA 4.9.2 there is a new
      error reported for ipa-rmkeytab in case of a non existing keytab file.
      Using ipa-rmkeytab now results in the error #7 in this case.
      
      The client role is using ipa-rmkeytab and needs to ignore error #7 also.
      
      Fixes: #510 (ipa-client installation with OTP is failed with error code 7
                   (keytab: /usr/sbin/ipa-rmkeytab returned 7))
      976cd1ba
  2. Feb 04, 2021
  3. Feb 02, 2021
  4. Feb 01, 2021
  5. Jan 27, 2021
  6. Jan 26, 2021
  7. Jan 18, 2021
  8. Jan 12, 2021
    • Rafael Guterres Jeffman's avatar
      Improve ipapermission member management. · 71c0972b
      Rafael Guterres Jeffman authored
      In `ipapermission` plugin, Some attributtes were not being managed
      when `action: member` was enabled.
      
      This patch enable member management for `right`, `rawfilter`,
      `filter, and fixes management of `memberof`.
      
      Fix issue #489
      71c0972b
  9. Jan 11, 2021
  10. Jan 08, 2021
  11. Jan 07, 2021
  12. Jan 06, 2021
    • Eric Nothen's avatar
      Enabled Ansible check_mode · 7bbb401b
      Eric Nothen authored
      Added code to the ipa* plugins to support Ansible's check_mode, by
      means of a clean exit before the execution of the actual list of
      commands that would otherwise create/update/delete IPA servers
      and/or its resources.
      7bbb401b
  13. Jan 04, 2021
    • Rafael Guterres Jeffman's avatar
      Fix changing the type of an existing Vault. · 7e04a46f
      Rafael Guterres Jeffman authored
      Current implementation does not allow the change of an existingi Vault
      type. To allow it, data is retrieved from the current vault, the vault
      is modifiend, and then, data is stored again in the new vault.
      
      Due to changing the process of modifying a vault, this change also
      fixes the update of asymmetric vault keys. To change the key used,
      the task must provide the old private key, used to retrieve data,
      and the new public_key, used to store the data again. A new alias
      was added to public_key (new_public_key) and public_key_file
      (new_public_key_file) so that the playbook better express the
      intention of the tak.
      
      Vault tests have been updated to better test against the new update
      process, and a new test file has bee added:
      
          tests/vault/test_vault_change_type.
      7e04a46f
  14. Dec 29, 2020
  15. Dec 22, 2020