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.
DescriptionAleksei Slaikovskii
2018-05-31 14:36:19 UTC
Document URL:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/linux_domain_identity_authentication_and_policy_guide
Section Number and Name:
22.2.6. Migrating from a Proprietary OTP Solution
kdc <-> ipa-otpd timeouts (currently ~5secs) and closes connection before remote radiusproxy could respond with access decision. For example, when radiusproxy is on slow network, some proprietary software, cloud service or is waiting for user response via 2FA.
There is a lack of description configuring time-outs in documentation. Some hints could be found at [1]. Original poster suggests editing /var/kerberos/krb5kdc/kdc.conf and restarted krb5kdc service:
[otp]
DEFAULT = {
timeout = 120
retries = 0
strip_realm = false
}
This allows to tune time-out according to one's needs.
[1] https://www.redhat.com/archives/freeipa-users/2016-December/msg00235.html