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.
Identity Management is aligning its existing FreeRADIUS offering with its strategic direction. Reduce freeradius authentication backends to the set to best enable the following supported use cases and drop the rest:
[1] Using FreeRADIUS as a wireless-authentication server with IdM as the backend source of authentication (via krb5 and LDAP authentication packages or via PAM authentication in the main FreeRADIUS package).
[2] Using FreeRADIUS to provide a source-of-truth for authentication in IdM (via the Python3 authentication package).
Note that use cases covered by the core freeradius package will not be affected. In particular, no RADIUS protocols (or extensions, such as EAP) are directly affected by these changes. This is strictly about exposure to other packages.
Packages to keep:
freeradius
freeradius-devel
freeradius-doc
freeradius-ldap
freeradius-krb5
python3-freeradius (requested in #1773636 and #1623069)
freeradius-utils
Packages to drop:
freeradius-{mysql,postgresql,sqlite,unixODBC}
freeradius-perl
freeradius-rest
Identity Management is aligning its existing FreeRADIUS offering with its strategic direction. Reduce freeradius authentication backends to the set to best enable the following supported use cases and drop the rest: [1] Using FreeRADIUS as a wireless-authentication server with IdM as the backend source of authentication (via krb5 and LDAP authentication packages or via PAM authentication in the main FreeRADIUS package). [2] Using FreeRADIUS to provide a source-of-truth for authentication in IdM (via the Python3 authentication package). Note that use cases covered by the core freeradius package will not be affected. In particular, no RADIUS protocols (or extensions, such as EAP) are directly affected by these changes. This is strictly about exposure to other packages. Packages to keep: freeradius freeradius-devel freeradius-doc freeradius-ldap freeradius-krb5 python3-freeradius (requested in #1773636 and #1623069) freeradius-utils Packages to drop: freeradius-{mysql,postgresql,sqlite,unixODBC} freeradius-perl freeradius-rest