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

ExternalCA : cert in master ca.p12 backup file should be imported regardless of cert validity #2610

Closed
pki-bot opened this issue Oct 3, 2020 · 5 comments

Comments

@pki-bot
Copy link

pki-bot commented Oct 3, 2020

This issue was migrated from Pagure Issue #2490. Originally filed by gkapoor (@geetikakay) on 2016-09-28 17:59:27:


If master and clone machines clock are out of sync that we see these issues
wherein certificates won't get imported in nssdb and when during installation
we do a nickname validation installation failed.

Steps to Reproduce:

1.Try to do externalCA installation
2.Installation test files can be picked from
https://bugzilla.redhat.com/show_bug.cgi?id=1379542

Actual results:

Installation fails in step2.

Expected results:

installation should pass.

Additional info:

debug logs are attached to corresponding bug
@pki-bot pki-bot added this to the 10.5.0 milestone Oct 3, 2020
@pki-bot pki-bot closed this as completed Oct 3, 2020
@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from mharmsen (@mharmsen) at 2016-10-04 22:43:05

Per CS/DS Meeting of 10/04/2016: 10.4

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from gkapoor (@geetikakay) at 2017-02-27 14:11:08

Metadata Update from @geetikakay:

  • Issue set to the milestone: UNTRIAGED

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from mharmsen (@mharmsen) at 2017-09-01 11:34:57

edewata wrote:

clone's clock must be synchronized. server won't start with invalid cert even if it's imported successfully.

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from mharmsen (@mharmsen) at 2017-09-01 11:34:59

Metadata Update from @mharmsen:

  • Custom field feature adjusted to None
  • Custom field proposedmilestone adjusted to None
  • Custom field proposedpriority adjusted to None
  • Custom field reviewer adjusted to None
  • Custom field version adjusted to None
  • Issue close_status updated to: invalid
  • Issue set to the milestone: 10.5 (was: UNTRIAGED)
  • Issue status updated to: Closed (was: Open)

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from mharmsen (@mharmsen) at 2017-09-06 19:40:15

Metadata Update from @mharmsen:

  • Issue set to the milestone: 10.5.0 (was: 10.5)

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

No branches or pull requests

1 participant