#2730 CLI: ca-kraconnector cli is not working as expected.
Closed: migrated 3 years ago by dmoluguw. Opened 6 years ago by mharmsen.

Test Case 1: If no KRA is configured annd we try to remove the KRA .

pki -p 8080 -d CMC1 -c Secret.123 -n "PKI Administrator for example.com"
ca-kraconnector-del --host pki1.example.com --port 8080
WARNING: BAD_CERT_DOMAIN encountered on
'CN=pki1.example.com,OU=pki-tomcat,O=example.com Security Domain' indicates a
common-name mismatch


Removed KRA host "pki1.example.com:8080"

Test Case 2:

Now install KRA and see what happens if we try to remove it and then so a
ca-kraconnector-show to see if the Kra connector is displaying after deleteting
it.

First install KRA::

[root@pki1 ~]# pki -p 8080 -d CMC1 -c Secret.123 -n "PKI Administrator for
example.com" ca-kraconnector-show
WARNING: BAD_CERT_DOMAIN encountered on
'CN=pki1.example.com,OU=pki-tomcat,O=example.com Security Domain' indicates a
common-name mismatch

Host: pki1.example.com:8443
Enabled: true
Local: false
Timeout: 30
URI: /kra/agent/kra/connector
Transport Cert:

MIIDwjCCAqqgAwIBAgIBBzANBgkqhkiG9w0BAQsFADBcMSQwIgYDVQQKDBtleGFt
cGxlLmNvbSBTZWN1cml0eSBEb21haW4xEzARBgNVBAsMCnBraS10b21jYXQxHzAd
BgNVBAMMFkNBIFNpZ25pbmcgQ2VydGlmaWNhdGUwHhcNMTcwNjA2MDkwMzM2WhcN
MTkwNTI3MDkwMzM2WjBfMSQwIgYDVQQKDBtleGFtcGxlLmNvbSBTZWN1cml0eSBE
b21haW4xEzARBgNVBAsMCnBraS10b21jYXQxIjAgBgNVBAMMGURSTSBUcmFuc3Bv
cnQgQ2VydGlmaWNhdGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCv
KSsjpMDBcBYKHEKya1HmGvGki2YpifDN1pRCMwLEp4RMRcMYm4ckPLymVOY4epRd
R45g/Xl0vtZ/qm3AUej7gceflCmo7rGbfVkZxCYPuVbFAGOtro4/aLgfuDPz2kgG
VoDCiHt08K7lkp4rdfTs0DIGIc0yDPT+raHCT3+Gzv0nNFFZDTn/NPSF+vcc5eRE
lMD0pI5vpspuWO7WFJ7cF51UXLJ3y20smzp9HQyeoAzE6BrSktN8lq5fdtWAznz1
RSVqCUcwtlPs13xv7Qy8FxAcB7ylYMLwIkqIlsC8oQRGex7lev2kd25+OgaEl8+J
fYa9uT8x+AFrJY/3IBpHAgMBAAGjgYswgYgwHwYDVR0jBBgwFoAUGFOWDx/LVX4H
B631m3Ir94pXwZEwQAYIKwYBBQUHAQEENDAyMDAGCCsGAQUFBzABhiRodHRwOi8v
cGtpMS5leGFtcGxlLmNvbTo4MDgwL2NhL29jc3AwDgYDVR0PAQH/BAQDAgTwMBMG
A1UdJQQMMAoGCCsGAQUFBwMCMA0GCSqGSIb3DQEBCwUAA4IBAQBkthg7RiGZKkmf
1AuXy9i+KnKjW1D8Y9sCxv1yaBAbVaiIni+s5aAbox9pChDruq51YPzUoIOhWrC8
QHQdRfsR0VmiqI3bnVtd8Lgd2ylggH4o6ANPTvPeH9nKUml0b+AxTW+cTHEI5rOi
dlFRSbBo1BnbPc5Xd55JC9z8r8cVnv1SAhG/AWIj5oOUsEFsfakmpzPo8I/snnu9
r0HTQPYc/v3zPJevKzW3UycWxzT58Mqyez2w7s/8rq1asv2Dm58Weqo1REHi3cxS
LrmavepTLQaU0mhD9CMbgbyVAzsZSuyqsRruw1OLTB81sWEk6fayx8ji/+I/fHbZ
yn1BXTvt

Delete KRA:

[root@pki1 ~]# pki -p 8080 -d CMC1 -c Secret.123 -n "PKI Administrator for
example.com" ca-kraconnector-del --host pki1.example.com --port 8080
WARNING: BAD_CERT_DOMAIN encountered on
'CN=pki1.example.com,OU=pki-tomcat,O=example.com Security Domain' indicates a
common-name mismatch


Removed KRA host "pki1.example.com:8080"

Do a show command to see if KRA still shows up.==>This output looks unexpected

[root@pki1 ~]# pki -p 8080 -d CMC1 -c Secret.123 -n "PKI Administrator for
example.com" ca-kraconnector-show
WARNING: BAD_CERT_DOMAIN encountered on
'CN=pki1.example.com,OU=pki-tomcat,O=example.com Security Domain' indicates a
common-name mismatch

Host: pki1.example.com:8443
Enabled: true
Local: false
Timeout: 30
URI: /kra/agent/kra/connector
Transport Cert:

MIIDwjCCAqqgAwIBAgIBBzANBgkqhkiG9w0BAQsFADBcMSQwIgYDVQQKDBtleGFt
cGxlLmNvbSBTZWN1cml0eSBEb21haW4xEzARBgNVBAsMCnBraS10b21jYXQxHzAd
BgNVBAMMFkNBIFNpZ25pbmcgQ2VydGlmaWNhdGUwHhcNMTcwNjA2MDkwMzM2WhcN
MTkwNTI3MDkwMzM2WjBfMSQwIgYDVQQKDBtleGFtcGxlLmNvbSBTZWN1cml0eSBE
b21haW4xEzARBgNVBAsMCnBraS10b21jYXQxIjAgBgNVBAMMGURSTSBUcmFuc3Bv
cnQgQ2VydGlmaWNhdGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCv
KSsjpMDBcBYKHEKya1HmGvGki2YpifDN1pRCMwLEp4RMRcMYm4ckPLymVOY4epRd
R45g/Xl0vtZ/qm3AUej7gceflCmo7rGbfVkZxCYPuVbFAGOtro4/aLgfuDPz2kgG
VoDCiHt08K7lkp4rdfTs0DIGIc0yDPT+raHCT3+Gzv0nNFFZDTn/NPSF+vcc5eRE
lMD0pI5vpspuWO7WFJ7cF51UXLJ3y20smzp9HQyeoAzE6BrSktN8lq5fdtWAznz1
RSVqCUcwtlPs13xv7Qy8FxAcB7ylYMLwIkqIlsC8oQRGex7lev2kd25+OgaEl8+J
fYa9uT8x+AFrJY/3IBpHAgMBAAGjgYswgYgwHwYDVR0jBBgwFoAUGFOWDx/LVX4H
B631m3Ir94pXwZEwQAYIKwYBBQUHAQEENDAyMDAGCCsGAQUFBzABhiRodHRwOi8v
cGtpMS5leGFtcGxlLmNvbTo4MDgwL2NhL29jc3AwDgYDVR0PAQH/BAQDAgTwMBMG
A1UdJQQMMAoGCCsGAQUFBwMCMA0GCSqGSIb3DQEBCwUAA4IBAQBkthg7RiGZKkmf
1AuXy9i+KnKjW1D8Y9sCxv1yaBAbVaiIni+s5aAbox9pChDruq51YPzUoIOhWrC8
QHQdRfsR0VmiqI3bnVtd8Lgd2ylggH4o6ANPTvPeH9nKUml0b+AxTW+cTHEI5rOi
dlFRSbBo1BnbPc5Xd55JC9z8r8cVnv1SAhG/AWIj5oOUsEFsfakmpzPo8I/snnu9
r0HTQPYc/v3zPJevKzW3UycWxzT58Mqyez2w7s/8rq1asv2Dm58Weqo1REHi3cxS
LrmavepTLQaU0mhD9CMbgbyVAzsZSuyqsRruw1OLTB81sWEk6fayx8ji/+I/fHbZ
yn1BXTvt

Steps to Reproduce:

try to do pki ca-kraconnector cli.

Expected results:

1. Test case 1 :

If no KRA exist we still display message that KRA is deleted.

2. Test Case 2:

Once we delete ca-kraconnector so after that if we do a show nothing should be
displayed as we have deleted it.

Metadata Update from @mharmsen:
- Custom field component adjusted to General
- Custom field feature adjusted to ''
- Custom field origin adjusted to Community
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1459093
- Custom field type adjusted to defect
- Custom field version adjusted to ''
- Issue set to the milestone: 10.5

6 years ago

Metadata Update from @mharmsen:
- Issue priority set to: major
- Issue set to the milestone: FUTURE (was: 10.5)

6 years ago

Metadata Update from @mharmsen:
- Custom field lowhangingfruit adjusted to vakwetu: X

6 years ago

Per 10.5.x/10.6 Triage: FUTURE

jmagne: connector is really gone, but the cli still lists it. Nice to fix.

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/2850

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

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)

3 years ago

Login to comment on this ticket.

Metadata