From Fedora Project Wiki
No edit summary
No edit summary
Line 2: Line 2:
|name=Database Server
|name=Database Server
|core=
|core=
# Multiple clients must be able to enroll and unroll in the domain
# Multiple clients must be able connect to the DB Server
# Client systems must be able to authenticate users with Kerberos
# The FreeIPA configuration web UI must be available and allow at least basic configuration of the DB.
# The FreeIPA configuration web UI must be available and allow at least basic configuration of user accounts and permissions
# Must allow external software to edit the DB.
|requirements=
|requirements=
# The Domain Controller must be capable of serving LDAP requests, including TLS-encrypted LDAP requests, on port 389
# The Domain Controller must be capable of serving LDAP requests, including TLS-encrypted LDAP requests, on port 389

Revision as of 19:55, 20 February 2015

This page contains the functional requirements for the Database Server role - that is, the things the role is expected to do when it's working properly. If Database Server is a Featured Role, then according to the Fedora_Release_Criteria, these requirements must be met to some extent for each Fedora Server pre-release and release: refer to the criteria pages for the exact details of which requirements must be met at each milestone.

Unless otherwise stated, it is always assumed that the role has been correctly deployed and configured by the system administrator.

Core requirements

  1. Multiple clients must be able connect to the DB Server
  2. The FreeIPA configuration web UI must be available and allow at least basic configuration of the DB.
  3. Must allow external software to edit the DB.

Requirements

  1. The Domain Controller must be capable of serving LDAP requests, including TLS-encrypted LDAP requests, on port 389
  2. The Domain Controller must be capable of serving LDAPS (LDAP encrypted with SSL) requests on port 636
  3. The Domain Controller must be capable of returning LDAP and LDAPS search results using simple auth or SASL/GSSAPI auth
  4. The Domain Controller must be capable of serving DNS host records on port 53
  5. The Domain Controller must serve DNS SRV records for LDAP and Kerberos on port 53

Test cases

  1. QA:Testcase_realmd_join_sssd (and other realmd_join tests in Category:Realmd_Test_Cases)
  2. QA:Testcase FreeIPA web ui