The framework port is hardcoded in our framework admin tool in ipalib/rpc.py::make_connection. It is hardcoded to 443.
If one tries to pass in a port in the RPC url it gets interpreted as part of the hostname:
ipa: ERROR: cannot connect to 'https://ipa.example.com:443/ipa/json': Cannot resolve iap.example.com:443 using family PR_AF_UNSPEC: (PR_ADDRESS_NOT_SUPPORTED_ERROR) Network address type not supported.
While this would increase FreeIPA flexibility, there is no known solid use case for it. Given the implementation&especially testing would be expensive, I am deferring it for now.
Metadata Update from @rcritten: - Issue assigned to someone - Issue set to the milestone: Tickets Deferred
Thank you taking time to submit this request for FreeIPA. Unfortunately this bug was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfil this request I am closing the issue as wontfix. To request re-consideration of this decision please reopen this issue and provide additional technical details about its importance to you.
Metadata Update from @rcritten: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.