Misleading naming used in documentation and code about certain certificates #5937
Assignees
Labels
Comments
|
Yeah, I'd noticed that when the code had originally been merged but we kept putting off fixing it. |
kodiakhq bot
pushed a commit
that referenced
this issue
Jan 14, 2022
This affects the certd config generated by running `iotedge config apply`, as well as a new Edge CA cert issued when the current one expires *and* the common name has not been set explicitly in certd config already. Fixes #5937 Ref #4740 Also fix iotedge-check tests to not require sudo access. Ref #5927 (comment)
lt72
pushed a commit
to lt72/iotedge
that referenced
this issue
Jan 31, 2022
…5998) This affects the certd config generated by running `iotedge config apply`, as well as a new Edge CA cert issued when the current one expires *and* the common name has not been set explicitly in certd config already. Fixes Azure#5937 Ref Azure#4740 Also fix iotedge-check tests to not require sudo access. Ref Azure#5927 (comment)
damonbarry
added a commit
to damonbarry/iotedge
that referenced
this issue
Apr 15, 2022
…5998) This affects the certd config generated by running `iotedge config apply`, as well as a new Edge CA cert issued when the current one expires *and* the common name has not been set explicitly in certd config already. Fixes Azure#5937 Ref Azure#4740 Also fix iotedge-check tests to not require sudo access. Ref Azure#5927 (comment)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
It would be good if documentation and code is aligned on the terminology used to describe various types of certificates.
Current Behavior
In here, it is said that
workload CA certificate was deprecated.When using IoT Edge with default settings, the common name of the certificate that the Edge Hub use is
iotedged workload ca(coming from this line). The naming sounds misaligned with the deprecation note in the documentation.The text was updated successfully, but these errors were encountered: