From Fedora Project Wiki

Scripted user creation

The scripted installation mechanism must provide a working function for creating local user accounts, including the ability to specify a hashed password, and for specifying a hashed password for the root account.

Remote authentication

It must be possible to join the system to a FreeIPA or Active Directory domain at install time and post-install, and the system must respect the identity, authentication and access control configuration provided by the domain.

Post-install requirements

Expected installed system boot behavior

  • A working mechanism to create a user account must be clearly presented during installation and/or first boot of the installed system.
  • Assuming no graphical desktop is installed, the installed system must boot to a state where it is possible to log in through at least one of the default virtual consoles.

System log forwarding

It must be possible to forward system logs between two systems running the release, using rsyslog.

Firewall configuration

After system installation without explicit firewall configuration, the system firewall must be active on all non-loopback interfaces. The only ports which may be open to incoming traffic are port 22 (ssh), port XX (Cockpit web interface), and any ports associated with server Roles selected during installation. Supported install-time firewall configuration options must work correctly.

SELinux configuration

Unless explicitly specified otherwise, after system installation SELinux must be enabled and in enforcing mode.

Cockpit management interface

Unless explicitly specified otherwise, after system installation the Cockpit web management interface must be running and accessible on its default port (XX).

Server Role requirements

The requirements in this section are understood to cover the behaviour of both supported roles themselves and the server role framework they use. Supported roles are defined as the roles promoted as supported in the Fedora Server release under test.

Role deployment

It must be possible to deploy supported roles successfully both at initial deployment time (during installation, or via a tool running on first boot after install, or both) and post-install.

Role service query

It must be possible to query supported roles for a list of services provided by the role, including information as to which are running and/or enabled.

Role firewall configuration

It must be possible to query supported roles for a list of network ports the role operates on, and whether those ports are firewalled. It must be possible to open and close these ports using the server role interface.

Role functional requirements

Supported roles must meet their functional requirements, as defined in their role specification documents.