LE certificate request requires a FQDN

[stephdl]

Steps to reproduce

• Install on NS8 an account provider
• Install a mail server
• Install webtop
• Configure webtop with a hostname foo
• request a LE certificate

Expected behavior

I expect to request a Let's encrypt certificate with the hostname foo

Actual behavior

Request a lest encrypt certificate needs several conditions but at least it won't never give with a hostname, it requires a fully qualified domain name as foo.com. The actual validator should block us and require a domain foo.com or a FQDN server.foo.com

Components

we have a lot module or core product impacted, in fact we used to validate with json schema like this

"format": "idn-hostname" "format": "hostname"

See also

https://mattermost.nethesis.it/nethesis/pl/k95kbw8ft3yf5gdtutwgszg18e

---

thank @lucagasparini

[stephdl]

• [x] ns8-mattermost OK
• [x] ns8-webtop OK
• [x] ns8-roundcubemail OK
• [ ] ns8-kickstart No validator in configure-module
• [x] ns8-nextcloud OK verification in https://github.com/NethServer/dev/issues/6865
• [x] ns8-imapsync OK
• [x] ns8-grafana OK
• [x] ns8-webserver OK
• [x] ns8-traefik set-route OK
• [x] ns8-mail OK
• [x] ns8-collabora OK
• [x] ns8-dokuwiki OK
• [x] ns8-minio OK
• [x] ns8-ejabberd OK
• [x] ns8-sogo OK
• [x] ns8-postgresql OK (released in nethforge)
• [x] ns8-kickstart-mariadb (merged)
• [x] ns8-kickstart-postgresql (merged)
• [ ] ...

[DavidePrincipi]

VERIFIED

The patch was verified for NextCloud https://github.com/NethServer/dev/issues/6865#issuecomment-1968792504

Let's close this issue. We will release individual modules in the upcoming weeks.

[stephdl]

closed, each module will be tested by the developer itself when a new release will occur