RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/5251

The current default for vaults is the standard vault.

The standard vault is a vault that can be acced by anyone that have access to the kra key and accessible by the framework directly.

The "standard  vault" is therefore not a good default as any admin can access it.

User's must take an actual explicit step to choose such a vault and they must be prominently warned that IPA administrator can access secrets stored in such a vault at any time.

The default vault should probably be the "symmetric vault".

Fixed upstream
master:
https://fedorahosted.org/freeipa/changeset/19dd2ed758210e859a5b0085de558cf13ba09104
ipa-4-2:
https://fedorahosted.org/freeipa/changeset/e247babc1ad211f7c939029cfb57eb6f4fbd79ab

Fixed upstream
master:
https://fedorahosted.org/freeipa/changeset/9b0a01930bcefda1f37d7de147fed0856c28296f
ipa-4-2:
https://fedorahosted.org/freeipa/changeset/91de475fd9d4499c05052e74bd2918569da4f269

Please provide steps to verify this.

adding of vault without any option should not create standard vault. The default vault type should be symmetric symmetric:

Expected result:

$ ipa vault-add abc 
New password: 
Verify password: 
-----------------
Added vault "abc"
-----------------
  Vault name: abc
  Type: symmetric             <<< -------- OK
  Salt: LD/aKS7TKhD6HHmeqGRYdw==
  Owner users: admin
  Vault user: admin


Without this fix. The "Type:" would be "standard".

Verified.

Version ::

ipa-server-4.2.0-8.el7.x86_64

Results ::

[root@master ~]# ipa vault-add mynewtestvault
New password: 
Verify password: 
----------------------------
Added vault "mynewtestvault"
----------------------------
  Vault name: mynewtestvault
  Type: symmetric
  Salt: AAswXbtArUxxWCHiEKho/Q==
  Owner users: admin
  Vault user: admin

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2362.html