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.

The setup for this problem is:
  ipa user-add foo
  ipa passwd foo
  kinit foo
  ipa otptoken-add

All of the above works. Now, let's actually enable OTP auth.

This works:
  ipa user-mod foo --user-auth-type=otp

This doesn't (but should):
  ipa config-mod --user-auth-type=otp

In both cases, doing a "kinit -T ... foo" prompts for OTP. In the first case, password + otp is required. In the second case, password-only is required.

Because kinit is prompting for OTP, this means KDB is working properly. Also, because password authentication works in the second case, it means that ipa-otpd is working properly. This means the ipapwd-extop plugin is ignoring the global setting.

This bug was caught by integration tests. I am *not* able to reproduce this bug on upstream FreeIPA, so this appears to be a RHEL specific issue.

Created attachment 985898 [details]
Patch proposal from Nathaniel

Verified using ipa-server-4.1.0-18.el7.x86_64


Steps taken:
Add two users:
# ipa user-add one --first=one --last=one --password
# ipa user-add two --first=two --last=two --password
Set their passwords:
# kinit one
# kinit two
# kinit admin
Add otp tokens for them:
# ipa otptoken-add --type=totp --owner=one --desc="My soft token"
# ipa otptoken-add --type=totp --owner=two --desc="My soft token"
# ipa user-mod one --user-auth-type=otp
Prepare to auth:
# klist
# kinit -T KEYRING:persistent:0:0 one
Can auth using password+otp only
# kinit -T KEYRING:persistent:0:0 two
since auth type is not set for two yet - auth'd using password
# kinit admin
# ipa config-mod --user-auth-type=otp
# kinit -T KEYRING:persistent:0:0 one
# kinit -T KEYRING:persistent:0:0 two
before fix, auth'd using password alone; after fix can auth using password+otp only

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/RHSA-2015-0442.html