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:
I have to NAT in to my network to access my idm server. When I setup port forwarding I should be able to port forward to idm.example.com:443 to access the webui and login. However, I get redirected to the FQDN:443 (removing the port) and that fqdn and port aren't routable on the external network.

Version-Release number of selected component (if applicable):


How reproducible:
everytime

Steps to Reproduce:
1. Setup idm
2. Try accessing the web console using the ip address (ex. https://192.168.1.12:443)

Actual results:
redirects to https://idm.example.com/ipa/ui


Expected results:
should redirect to https://192.168.1.12:443/ipa/ui

Additional info:
This works fine using Ansible Tower and Satellite 6. I can access and login to the webui from an external network using port forwarding.

For external network you may need https://www.adelton.com/freeipa/freeipa-behind-proxy-with-different-name

This is an intended behavior. There is a redirection rule in /etc/httpd/conf.d/ipa-rewrite.conf which does it.

Without it Kerberos authentication may not work.

*** This bug has been marked as a duplicate of bug 1466014 ***