This was more complicated than it probably should have been due to the IPA domain not matching the truenas host domain, I think.
dnf install ipa-server-trust-ad
ipa-adtrust-install
IPA.SIHNON.NEThost/fqdn@IPA.SIHNON.NET keytab/etc/krb5.conf: [libdefaults]
dns_lookup_realm = false # change from true
dns_lookup_kdc = false # change from true
[domain_realms]
# Add these two lines
jellybean.sihnon.net = IPA.SIHNON.NET
.jellybean.sihnon.net = IPA.SIHNON.NET
winbind serviceWhen connecting from a non-domain joined Windows, it won't prompt for credentials and will fail. Must explicitly map a drive, using IPA domain creds first. Subsequent connections to the same hostname will reuse the credentials, so not all shares need to be mapped.
For the first server, follow the below instructions.
tsig-keygen -a HMAC-SHA512
truenas.profile::freeipa::named::keys), and make sure bind has been restarted to pick up the changedata/system/acme datasetstruenas_admin and run the following: sudo chown truenas_admin /mnt/data/system/acme git clone --depth 1 https://github.com/acmesh-official/acme.sh.git
/mnt/data/system/acme/.nsupdate.key (making sure the key name and secret match puppet)
For subsequent servers, clone the acme filesystem
For all servers:
Credentials→CertificatesACME DNS-Authenticator/mnt/data/system/dns_acme.shrootCertificate Signing Request. Follow the wizard. LetsEncrypt doesn't use any of the subject attributes so set any values.Create ACME certificateletsencrypt CSR appears in the list, navigate to System-GeneralSettings buttonletsencrypt certificate under GUI SSL Certificate and save changes, confirming thr restart