Server-Side Security

The Server-side security page allows you to control the security settings or operations on the server-side of the platform. For example, it allows you to supply a custom encryption key for encryption on the internal network.

Tip: If you want to secure the client-side options, see Client Security.

Server-Side Security page

Access this page in the Admin Console by selecting Security > Server-Side Security in the left-hand menu:

Important: Always remember to apply any changes using the Apply button at the top-right of the workspace. Note that the Apply button is only enabled once you have added valid changes to the page.

Repository Encryption

Repository Encryption ensures that sensitive content being saved to the database (API keys, passwords, and so on) is encrypted.

Key

  • Use Custom Key: If you have your own custom key, select the checkbox and then paste your custom key into the text field. Your key must be a valid AES 256 key in base 64 format, with a string length of 32 bytes.
  • Generate: Alternatively, click Generate to get Pyramid to generate a new random key for you.

Note: Whenever you add or generate a new key, it begins to be used as soon as you apply your changes.

Validate server to server requests

Select the Validate server to server requests checkbox to validate all communications between Pyramid services. This ensures that requests originate from trusted services within the deployment and helps prevent unauthorized communications.

Internal network encryption

Internal network encryption encrypts communications between the Pyramid services internally. By default, internal network encryption is not enabled.

To enable internal encryption:

  1. Select Encrypted from this dropdown list.

    2. The Use Custom Key checkbox opens for this option.

  2. Select the Use Custom Key checkbox. You can select one of the following options:
    • By default, Pyramid will use either the last generated key or the default key.
    • Alternatively, you can enter a custom key (using Use Custom Key) or generate a new custom key (using Generate). Details are as described above.

Note: Enabling internal encryption may affect performance.

Note: This feature does not need to be enabled to use external encryption via SSL for the web client.

Delegate Kerberos for Windows Authentication

If you are using Windows Authentication as your authentication method, you can optionally turn this on to continue delegating authentication to Kerberos.

Kerberos tickets are only required when using Kerberos delegated authentication, currently with SAP BW Logon Tickets and MS SQL Server Relational Authentication with Windows Auth. This is not required for MS Analysis Services Authentication. Turning this off, if it is not needed, will positively impact performance.

Mobile Device Settings

Links to the Mobile Device Settings page. For more information, see Mobile Device Settings.