Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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/5003
OTP tokens have both an owner and a manager. However, only the owner is exposed in the UI.
Careful interaction is required here. In the current code, this also creates a bug since all UI created tokens are owned but not managed. When users of these tokens are deleted, their self-created tokens are orphaned rather than deleted.
Self-created tokens MUST be both self-owned AND self-managed.
Verifies using ipa-server-4.2.0-12.el7.x86_64
Steps taken to verify:
1> ipa user-add and added users one, two, three, four
2> ipa passwd one
3> Added a token, and assigned owner to be one: ipa otptoken-add --type=totp --owner=one --desc="My soft token" tokenOne
4> Updated one to auth using otp: ipa user-mod one --user-auth-type=otp
5> Added users to manage this token: ipa otptoken-add-managedby tokenOne --users={two,three}
6> ipa otptoken-show tokenOne --all
At every step above, verified UI reflected the changes and listed managers for the token.
Then did the above from UI, and added new token for user two. Updated and assigned new owner for the token successfully
Updated back to original owner using cli:
# ipa otptoken-mod tokenOneOne --owner=two
--------------------------------
Modified OTP token "tokenTwo"
--------------------------------
Unique ID: tokenTwo
Type: TOTP
Owner: two
Deleted user two in UI, and verified tokenTwo is listed in tokens, with no owner, and since it wasn't assigned a manager - no manager was listed either
next assigned this lone token to user four:
# ipa otptoken-mod tokenOneOne --owner=four
--------------------------------
Modified OTP token "tokenTwo"
--------------------------------
Unique ID: tokenTwo
Type: TOTP
Owner: four
Manager: four
And it got owner and manager assigned. Displayed the same in UI as well.
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