Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to access pki console after setting IPV6 address in pki console #2576

Open
pki-bot opened this issue Oct 3, 2020 · 4 comments
Open
Milestone

Comments

@pki-bot
Copy link

pki-bot commented Oct 3, 2020

This issue was migrated from Pagure Issue #2456. Originally filed by ssidhaye@redhat.com (@ssidhaye) on 2016-09-14 18:05:48:


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
@pki-bot pki-bot added this to the FUTURE milestone Oct 3, 2020
@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from ssidhaye@redhat.com (@ssidhaye) at 2017-02-27 14:09:33

Metadata Update from @ssidhaye:

  • Issue set to the milestone: UNTRIAGED

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from mharmsen (@mharmsen) at 2017-03-03 19:04:47

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)

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from mharmsen (@mharmsen) at 2017-08-09 12:45:15

Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from mharmsen (@mharmsen) at 2017-08-09 12:45:17

Metadata Update from @mharmsen:

  • Issue set to the milestone: FUTURE (was: 10.4)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant