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.

Description of problem:
[root@master ~]# ipa vault-add vname --service=service_dne
-------------------
Added vault "vname"
-------------------
  Vault name: vname
  Type: standard
  Owner users: admin
[root@master ~]# ipa vault-show vname 
ipa: ERROR: vname: vault not found
[root@master ~]# ipa vault-show vname --service=service_dne
  Vault name: vname
  Type: standard
  Owner users: admin


Version-Release number of selected component (if applicable):
ipa-server-4.2.0-4.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1.  ipa-server-install
2.  ipa-kra-install
3.  kinit admin
4.  ipa vault-add vname --service=service_dne

Actual results:
adds vault

Expected results:
should not add vault

Additional info:

Upstream ticket:
https://fedorahosted.org/freeipa/ticket/5215

Was discussed offline and was decided that creating a vault for non-existent user/service is a valid use-case.

Reopening this bug for either more detailed clarification of why adding a vault for a non-existent service is valid or to get this resolved.

IMHO, we should not add a service vault until after the service is added.


Thanks,
Scott

The reason is consistency with delete operation. Vault is not deleted when user is deleted to preserve secrets. So the state can be achieved even if it is not permitted.

Maybe the add operation can print a warning that the user|service doesn't exist, e.g. to solve "typo" mistakes.

A warning on add would be good but, is it possible instead to add a warning on user-del?  To me it seems better to error on vault-add and show a warning on user-del (if possible) that the vaults and containers must be manually removed.  This would prevent adding an initial orphan and/or prevent adding new ones for already deleted users.

I've opened https://fedorahosted.org/freeipa/ticket/5674 to reflect comment 6. 

It will be resolved according to the triage.

Since the proposal will be resolved elsewhere I'm closing this bug again.