There is Let’s Encrypt but it is not an obligation.
After installation of the server, there is a message to change the informations of the Company but the SSL/TLS certificate has not changed: “NethServer, O=Example Org, ST=SomeState, OU=Main”
1/ It will be easy to add the creation of a complete certificate (in nethgui and cockpit) manually.
Of course we do–it’s installed on the system by default. What benefit is there to changing the organization information on a cert that no browser is going to trust anyway? I guess it doesn’t matter that much what I think–I certainly don’t run the project, and I wouldn’t be implementing this in any event–but it really seems that any effort at all invested into improving a self-signed cert would be wasted effort.
I’m just not understanding the server admin who, at the same time:
Cares what information is presented with his server’s TLS certificate, and
Doesn’t care whether any browser in the world trusts that certificate.
…especially when it’s easy and free to get a trusted cert. IMO, the only reason to have the self-signed cert at all is to let the server speak TLS long enough for you to install a real cert.
Organization details and certificate were bound together and thatch choice created only problems.
The user is now free to change such info both on certificate page or on the organization details page.
I agree with @danb35: there is no reason to implement such a thing.
What is not really working? Can you please write down what is the expected behavior and what is missing? Can you also describe the steps to reproduce it?