Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fixed security domain authentication
Previously pkispawn would only connect to a security domain when installing a new subsystem that joins the security domain (pki_security_domain_type == existing). It also would only authenticate against the security domain if it's not skipping security domain verification (pki_skip_sd_verify == False), which is the default. When installing a subordinate CA with a new security (sub)domain it would have pki_security_domain_type == new, so it would not connect to nor authenticate against the parent security domain, and it would not be able to get the installation token required to complete the installation. The code has been modified such that pkispawn will connect to a security domain when installing a subsystem to join the security domain (pki_security_domain_type == existing) as before, but also when installing a subordinate CA (pki_subordinate == True). It will also authenticate against the security domain regardless of the pki_skip_sd_verify since the authenitcation is required to obtain the installation token. The surrounding try-catch block has also been removed since the original exception will have more detailed information (i.e. the exact URL) about the problem. https://bugzilla.redhat.com/show_bug.cgi?id=1807421
- Loading branch information