Skip to content

Commit 311ff51

Browse files
committed
fixing broken media link
1 parent 81cbb5b commit 311ff51

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/service-fabric/cluster-security-certificate-management.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -64,12 +64,12 @@ For our purposes, the first two steps in the sequence above are largely unrelate
6464
These steps are illustrated below; note the differences in provisioning between certificates declared by thumbprint and common name, respectively.
6565
<center>
6666

67-
![Journey of certificates declared by thumbprint][Image1]
67+
![Provisioning certificates declared by thumbprint][Image1]
6868
<center>
6969

7070
<center>
7171

72-
![Journey of certificates declared by subject common name][Image2]
72+
![Provisioning certificates declared by subject common name][Image2]
7373
<center>
7474

7575
### Certificate enrollment
@@ -490,5 +490,5 @@ For Microsoft-internal PKIs, the authority on, well, authorized issuers is the d
490490
Q: Are multiple PKIs supported?
491491
A: Yes; you may not declare multiple CN entries in the cluster manifest with the same value, but can list issuers from multiple PKIs corresponding to the same CN. It is not a recommended practice, and certificate transparency practices may prevent such certificates from being issued. However, as means to migrate from one PKI to another, this is an acceptable mechanism.
492492

493-
[Image1]:.media/security-cluster-certificate-mgmt/certificate-journey-thumbprint.png
493+
[Image1]:./media/security-cluster-certificate-mgmt/certificate-journey-thumbprint.png
494494
[Image2]:./media/security-cluster-certificate-mgmt/certificate-journey-common-name.png

0 commit comments

Comments
 (0)