Banners

There are two kind of banners, the pre-authentication banner is shown before the user logs in to the CipherTrust Manager server, and the post-authentication banner is shown after login. Both are optional and not set by default.

The pre-authentication banner is useful for displaying disclaimer or legal security policy. You must accept the terms identified in this banner in order to login. Not accepting the terms will prevent you from logging in to the CipherTrust Manager server.

The post-authentication banner is useful for displaying about the system. This banner message can be used to provide general information about the server to the user such as upcoming maintenance. The user is not asked to accept this banner message.

Viewing and updating the banner pages can be done using the CLI, GUI and API.

Banners support the unicode standard and the Markdown markup language.

Viewing the Banners using the CLI

Using the CLI, you can view the pre- and post-authentication banner by using the banners get command:

Example get commands:

$ ksctl banners get --name pre-auth

or

$ ksctl banners get --name post-auth

Default command response before updating the banner message, for each command is:

{
  "value": ""
}

Example response after updating the pre- or post authentication banner:

{
  "value": "Example text of the banner."
}

Updating the Banners using the CLI

You can update the pre- and post-authentication banners using the banners update command:

There are two ways to provide a new banner message:

• using the argument --message <banner-message> where <banner-message> is new banner message

• using the argument --file <banner-message-file>, where <banner-message-file> is a path and filename in Markdown notation containing the new banner message

  Example: /path/banner-message.md

Pre-auth Example update --message command:

$ ksctl banners update --name pre-auth --message "Before logging in to KeySecure, you must accept the following 'Terms of Use': ..."

Response:

{
  "value": "Before logging in to CipherTrust Manager, you must accept the following 'Terms of Use': ..."
}

Post-auth Example update --message command:

$ ksctl banners update --name post-auth --message "Welcome to **CipherTrust k170v Server**."

Response:

{
  "value": "Welcome to **CipherTrust k170v Server**."
}

Pre-auth Example update --file command:

$ ksctl banners update --name pre-auth --file </path/banner-message.md>

If the markdown file contains: "Before logging in to CipherTrust Manager, you must accept the following 'Terms of Use': ...", the response is:

{
  "value": "Before logging in to CipherTrust Manager, you must accept the following 'Terms of Use': ..."
}

Post-auth Example update --file command:

$ ksctl banners update --name post-auth --file </path/banner-message.md>

If the markdown file contains: "Welcome to **CipherTrust k170v Server**.", the response is:

{
  "value": "Welcome to **CipherTrust k170v Server**."
}