The Site Information panel provides read-only access to the site name, UUID, and public key, and includes the ability to re-generate the site’s public SSH key. The UUID and public key are automatically generated during the creation of the site record and are viewable after the site settings have been saved.
This is the name given to identify the site being edited. It is also the filename of the directory that contains the files for the site on the staging server. This cannot be changed once defined during site creation and should be unique to the account.
A site name cannot include spaces, but can include uppercase and lowercase letters, numeric values, hyphens, and underscores. It also should not include duplicated names even if the letter case is different. In other words, www and WWW would be an example of a duplicated name.
Note: When setting up the site structure (the sites that are created within the account), if it is desired that a site be set up with a subfolder, such as http://www.institution.edu/admissions, and that there will also be a site at just the domain root (e.g., http://www.institution.edu/), it is possible that users may create folders within the domain that essentially overwrites the contents of the other sites. Use caution when setting up this site structure.
An alternative site structure is to use a subdomain for each site. For example, the admissions department would be http://admissions.institution.edu/ and where the DNS is managed separately for each subdomain.
The read-only UUID is used with Live Delivery Platform.
The public key field displays the site’s SSH public key. This key can be used to create a secure connection from OU Campus to the production server without using a username and password combination. This is automatically generated after saving the site record when creating a site.
In order for Public Key Authentication to function properly, the OU Campus public key needs to be copied to the .ssh/authorized_keys file on the institution's production server.
More information regarding public keys can be found at this page on Ubuntu's documentation site.
The Generate button can be used to regenerate the public key for a site.
Warning: Be aware that if the server has already been configured to authenticate with a public key, re-generating a new key will break that existing connection and it will need to be re-configured on the server to authenticate with the new public key.
Additionally, if a site has been registered with an installation of an SSM on the production server, the site will need to be re-registered, as each site needs to be registered with the SSM in order to function properly. Registering a site adds the following to the SSM database:
- Site’s UUID
- Public Key
To regenerate the public key, click Generate and confirm.