When we setup Dogtag subsystems with IPV6, pki console is not accessible when we specify IPV6 address in "Internal Database" of pki console.
Steps to Reproduce:
1. Setup Dogtag subsystems with IPV6 2. Access pki console and mention the IPV6 address in "Internal Database" section 3. try accessing the pki console after adding the IPV6 address
Actual results:
Not able to access pki console.
Expected results:
pki console should be accessible even if we configure IPV6 address in pki console.
Additional info:
This is happening for all the subsystems
Metadata Update from @ssidhaye@redhat.com: - Issue set to the milestone: UNTRIAGED
Metadata Update from @mharmsen: - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: None - Issue set to the milestone: 10.4 (was: UNTRIAGED)
Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.
Metadata Update from @mharmsen: - Issue set to the milestone: FUTURE (was: 10.4)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2576
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.