{"id":3610,"date":"2023-12-27T13:52:34","date_gmt":"2023-12-27T04:52:34","guid":{"rendered":"http:\/\/192.168.20.1\/?p=3610"},"modified":"2024-01-01T11:48:03","modified_gmt":"2024-01-01T02:48:03","slug":"truenas-scale-create-server-csr","status":"publish","type":"post","link":"https:\/\/rlab.cavtime.net\/?p=3610","title":{"rendered":"[TrueNAS Scale] Create Server CSR"},"content":{"rendered":"<h2>Overview<\/h2>\n<p>TrueNAS Scale \u3067 CSR \u3092\u4f5c\u6210\u3059\u308b\u624b\u9806\u3092\u78ba\u8a8d\u3059\u308b\u3002<\/p>\n<h2>Reference<\/h2>\n<h2>Environment<\/h2>\n<p>TrueNAS Scale 23.10.0.1<\/p>\n<h2>Certificate Signing Requests<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/rlab.cavtime.net\/wp-content\/uploads\/2023\/12\/Credentials_Certificate_01s-1.png\" alt=\"\" width=\"900\" height=\"721\" class=\"img-responsive right-block\" \/><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/rlab.cavtime.net\/wp-content\/uploads\/2023\/12\/Credentials_Certificate_CSR_01s.png\" alt=\"\" width=\"900\" height=\"752\" class=\"img-responsive right-block\" \/><\/p>\n<h3>Identifier and Type<\/h3>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/rlab.cavtime.net\/wp-content\/uploads\/2023\/12\/Credentials_Certificate_CSR_02s.png\" alt=\"\" width=\"900\" height=\"765\" class=\"img-responsive right-block\" \/><\/p>\n<p><strong>Name<\/strong><\/p>\n<blockquote><p>Descriptive identifier for this certificate.<\/p><\/blockquote>\n<p><strong>Type<\/strong><\/p>\n<blockquote><p>Certificate Signing Requests control when an external CA will issue (sign) the certificate. Typically used with ACME or other CAs that most popular browsers trust by default Import Certificate Signing Request lets you import an existing CSR onto the system. Typically used with ACME or internal CAs.<\/p><\/blockquote>\n<ul>\n<li>Certificate Signing Request<\/li>\n<li>Import Certificate Signing Request<\/li>\n<\/ul>\n<p><strong>Profile<\/strong><\/p>\n<blockquote><p>Predefined certificate extensions. Choose a profile that best matches your certificate usage scenario.<\/p><\/blockquote>\n<ul>\n<li>HTTPS RSA Certificate<\/li>\n<li>HTTPS ECC Certificate<\/li>\n<\/ul>\n<h3><span>Certificate Options<\/span><\/h3>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/rlab.cavtime.net\/wp-content\/uploads\/2023\/12\/Credentials_Certificate_CSR_03s.png\" alt=\"\" width=\"900\" height=\"765\" class=\"img-responsive right-block\" \/><\/p>\n<p><strong>Key Type<\/strong><\/p>\n<blockquote><p>See Why is elliptic curve cryptography not widely used, compared to RSA? for more information about key types.<\/p><\/blockquote>\n<ul>\n<li>RSA<\/li>\n<li>EC<\/li>\n<\/ul>\n<p><strong>Key Length<\/strong><\/p>\n<blockquote><p>The number of bits in the key used by the cryptographic algorithm. For security reasons, a minimum key length of 2048 is recommended.<\/p><\/blockquote>\n<ul>\n<li>1024<\/li>\n<li>2048<\/li>\n<li>4096<\/li>\n<\/ul>\n<p><strong>Digest Algorithm<\/strong><\/p>\n<blockquote><p><span>The cryptographic algorithm to use. The default\u00a0<\/span><i>SHA256<\/i><span>\u00a0only needs to be changed if the organization requires a different algorithm.<\/span><\/p><\/blockquote>\n<ul>\n<li>SHA1<\/li>\n<li>SHA224<\/li>\n<li>SHA256<\/li>\n<li>SHA384<\/li>\n<li>SHA512<\/li>\n<\/ul>\n<h3><span>Certificate Subject<\/span><\/h3>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/rlab.cavtime.net\/wp-content\/uploads\/2023\/12\/Credentials_Certificate_CSR_04s.png\" alt=\"\" width=\"900\" height=\"1162\" class=\"img-responsive right-block\" \/><\/p>\n<p><strong>Country<\/strong><\/p>\n<blockquote><p>Select the country of the organization.<\/p><\/blockquote>\n<ul>\n<li>United State \/ default<\/li>\n<li>and others<\/li>\n<\/ul>\n<p><strong>State<\/strong><\/p>\n<blockquote><p><span>Enter the state or province of the organization.<\/span><\/p><\/blockquote>\n<p><strong>Locality<\/strong><\/p>\n<blockquote><p><span>Enter the location of the organization. For example, the city.<\/span><\/p><\/blockquote>\n<p><strong>Organization<\/strong><\/p>\n<blockquote><p><span>Enter the name of the company or organization.<\/span><\/p><\/blockquote>\n<p><strong>Organizational Unit<\/strong><\/p>\n<blockquote><p><span>Organizational unit of the entity.<\/span><\/p><\/blockquote>\n<p><strong>Email<\/strong><\/p>\n<blockquote><p><span>Enter the email address of the person responsible for the CA.<\/span><\/p><\/blockquote>\n<p><strong>Common Name<\/strong><\/p>\n<blockquote><p>Enter the fully-qualified hostname (FQDN) of the system. This name must be unique within a certificate chain.<\/p><\/blockquote>\n<p><strong>Subject Alternative Name<\/strong><\/p>\n<blockquote><p><span>Multi-domain support. Enter additional domains to secure. Separate domains by pressing\u00a0<\/span><code>Enter<\/code><span>\u00a0For example, if the primary domain is\u00a0<\/span><i>example.com<\/i><span>, entering\u00a0<\/span><i>www.example.com<\/i><span>\u00a0secures both addresses.<\/span><\/p><\/blockquote>\n<h3>Extra Constraints<\/h3>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/rlab.cavtime.net\/wp-content\/uploads\/2023\/12\/Credentials_Certificate_CSR_05s.png\" alt=\"\" width=\"900\" height=\"1011\" class=\"img-responsive right-block\" \/><\/p>\n<p><strong>Basic Constraints<\/strong><\/p>\n<blockquote><p><span>Activate the Basic Constraints extension to identify whether the certificate&#8217;s subject is a CA and the maximum depth of valid certification paths that include this certificate.<\/span><\/p><\/blockquote>\n<ul>\n<li>Checked \/ default<\/li>\n<\/ul>\n<p><strong>Path Length<\/strong><\/p>\n<blockquote><p><span>How many non-self-issued intermediate certificates that can follow this certificate in a valid certification path. Entering\u00a0<\/span><i>0<\/i><span>\u00a0allows a single additional certificate to follow in the certificate path. Cannot be less than\u00a0<\/span><i>0<\/i><span>.<\/span><\/p><\/blockquote>\n<p><strong>Basic Constraints Config<\/strong><\/p>\n<blockquote><p><span>Specify whether to use the certificate for a Certificate Authority and whether this extension is critical. Clients must recognize critical extensions to prevent rejection. Web certificates typically require you to disable CA and enable Critical Extension.<\/span><\/p><\/blockquote>\n<ul>\n<li>CA \/ unselect<\/li>\n<li>Critical Extension \/ unselect<\/li>\n<\/ul>\n<p><strong>Extended Key Usage<\/strong><\/p>\n<blockquote><p><span>Activate this certificate extension.The Extended Key Usage extension identifies and limits valid uses for this certificate, such as client authentication or server authentication.See\u00a0<\/span><a href=\"https:\/\/www.ietf.org\/rfc\/rfc3280.txt\" target=\"_blank\" rel=\"noopener\">RFC 3280, section 4.2.1.13<\/a><span>\u00a0for more details.<\/span><\/p><\/blockquote>\n<ul>\n<li>Checked \/ default<\/li>\n<\/ul>\n<p><strong>Usages<\/strong><\/p>\n<blockquote><p>Identify the purpose for this public key. Typically used for end entity certificates. Multiple usages can be selected. Do not mark this extension critical when the Usage is ANY_EXTENDED_KEY_USAGE.<\/p>\n<p>Using both Extended Key Usage and Key Usage extensions requires that the purpose of the certificate is consistent with both extensions. See RFC 3280, section 4.2.1.13 for more details.<\/p><\/blockquote>\n<ul>\n<li>ANY_EXTENDED_KEY_USAGE<\/li>\n<li>CERTIFICATE_TRANSPARENCY<\/li>\n<li>CLIENT_AUTH \/ Selected<\/li>\n<li>CODE_SIGNING<\/li>\n<li>EMAIL_PROTECTION<\/li>\n<li>IPSEC_IKE<\/li>\n<li>KERBEROS_PKINIT_KDC<\/li>\n<li>OCCP_SIGNING<\/li>\n<li>SERVER_AUTH \/ Selected<\/li>\n<li>SMARTCARD_LOGON<\/li>\n<li>TIME_STAMPING<\/li>\n<\/ul>\n<p><strong>Critical Extension<\/strong><\/p>\n<blockquote><p>Identify this extension as critical for the certificate. Critical extensions must be recognized by the certificate-using system or this certificate will be rejected. Extensions identified as not critical can be ignored by the certificate-using system and the certificate still approved.<\/p><\/blockquote>\n<ul>\n<li>Checked \/ default<\/li>\n<\/ul>\n<p><strong>Key Usage<\/strong><\/p>\n<blockquote><p><span>Activate this certificate extension. The key usage extension defines the purpose (e.g., encipherment, signature, certificate signing) of the key contained in the certificate. The usage restriction might be employed when a key that could be used for more than one operation is to be restricted. For example, when an RSA key should be used only to verify signatures on objects other than public key certificates and CRLs, the\u00a0<\/span><i>Digital Signature<\/i><span>\u00a0bits would be asserted. Likewise, when an RSA key should be used only for key management, the\u00a0<\/span><i>Key Encipherment<\/i><span>\u00a0bit would be asserted.<\/span><br \/>\n<span>See\u00a0<\/span><a href=\"https:\/\/www.ietf.org\/rfc\/rfc3280.txt\">RFC 3280, section 4.2.1.3<\/a><span>\u00a0for more information.<\/span><\/p><\/blockquote>\n<ul>\n<li>Checked \/ default<\/li>\n<\/ul>\n<p><strong>Key Usage Config<\/strong><\/p>\n<blockquote><p><span>Specify this certificate&#8217;s valid Key Usages. Web certificates typically need at least Digital Signature and possibly Key Encipherment or Key Agreement, while other applications may need other usages.<\/span><\/p><\/blockquote>\n<ul>\n<li>Digital Signature \/ Selected<\/li>\n<li>Content Commitment<\/li>\n<li>Key Enciphement \/ Selected<\/li>\n<li>Date Enciphement<\/li>\n<li>Key Agreement \/ Selected<\/li>\n<li>Key Cert Sign<\/li>\n<li>CRL Sign<\/li>\n<li>Encipher Only<\/li>\n<li>Decipher Only<\/li>\n<li>Critical Extension \/ Selected<\/li>\n<\/ul>\n<h3>Confirm Options<\/h3>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/rlab.cavtime.net\/wp-content\/uploads\/2023\/12\/Credentials_Certificate_CSR_06s.png\" alt=\"\" width=\"900\" height=\"938\" class=\"img-responsive right-block\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Overview TrueNAS Scale \u3067 CSR \u3092\u4f5c\u6210\u3059\u308b\u624b\u9806\u3092\u78ba\u8a8d\u3059\u308b\u3002 Reference Environment TrueNAS Scale 23.10.0.1 Certificate Signing R [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[37,74],"tags":[],"class_list":["post-3610","post","type-post","status-publish","format-standard","hentry","category-certificate","category-nas"],"_links":{"self":[{"href":"https:\/\/rlab.cavtime.net\/index.php?rest_route=\/wp\/v2\/posts\/3610","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rlab.cavtime.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rlab.cavtime.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rlab.cavtime.net\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/rlab.cavtime.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3610"}],"version-history":[{"count":2,"href":"https:\/\/rlab.cavtime.net\/index.php?rest_route=\/wp\/v2\/posts\/3610\/revisions"}],"predecessor-version":[{"id":3661,"href":"https:\/\/rlab.cavtime.net\/index.php?rest_route=\/wp\/v2\/posts\/3610\/revisions\/3661"}],"wp:attachment":[{"href":"https:\/\/rlab.cavtime.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3610"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rlab.cavtime.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3610"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rlab.cavtime.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3610"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}