[Docs] Certificate documentation doesn't actually show how route53 or cloudflare need to be setup
Description
Problem/Justification
Impact
Activity
Automation for Jira January 18, 2023 at 12:13 PM
This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.
Michelle Johnson January 18, 2023 at 12:13 PM
Issue closed, and converted to a Product Documentation ticket.
Kjeld Schouten-lebbing January 18, 2023 at 12:12 PM
Thanks, yes a “Product Documentation request” was what I was basically asking for, but cannot create myself.
Thank you!
Michelle Johnson January 18, 2023 at 12:11 PM
Thank you for your report, !
And thank you for the feedback on our current certificates related documentation. We plan to expand these topics and add tutorial content in the near future. We are waiting on resources that will allow us to set up, test, and fully document the certificates, CAs, CSRs. and ACME DNS Authenticators. Our current resources do not allow us the freedom to work in this area but we have requested they be provisioned for us. We look forward to your feedback. I’m going to close this issue ticket and open a Product Documentation request (it will be linked to this issue ticket).
Automation for Jira January 17, 2023 at 12:39 PM
Thank you for submitting this TrueNAS Bug Report! So that we can quickly investigate your issue, please attach a Debug file and any other information related to this issue through our secure and private upload service below. Debug files can be generated in the UI by navigating to System -> Advanced -> Save Debug.
https://ixsystems.atlassian.net/servicedesk/customer/portal/15/group/37/create/153
The Current Certificate documentation is a HUGE step up from what was previously there.
However: Some important parts are missing from the ACME documentation…
Both for Cloudflare and Route53, the docs do not actually show what those credential fields refer to in the Cloudflare and Route53 interface respectively and/or if any additional configuration is required.
Primarily Route53 with ACME seems to be rather complicated when it comes to these.
Reporting as a documentation-bug, because having these things undocumented in an already relatively complicated setup process, is going to overwhelm the user. Primarily the Route53 option, is currently not feasable to be deployed at all by a non-aws professional.