Your suggested change has been received. Thank you.

close

Suggest A Change

https://thales.na.market.dpondemand.io/docs/dpod/services/kmo….

Thales Logo

All

  • All
back

CipherTrust Manager Administration

Scheduler

search

Please Note:

Scheduler

Note

This feature is not included in Community Edition and requires a valid Virtual CipherTrust Manager license. To activate your instance with a trial evaluation, or a term or perpetual license, see Licensing.

The CipherTrust Manager can periodically run key rotation, database backup, and user password expiry notification jobs in the background. These jobs can be:

  • Configured using the scheduler

  • Scheduled by creating a job configuration

A job configuration defines what job is run and when. Job configurations can be read, listed, updated, and deleted. Jobs are run after job configurations are created. The jobs that were run can also be listed.

In a clustered environment, by default the scheduled job can run on any cluster node. There is an option in the API and CLI to restrict which nodes can run the scheduled job.

This section provides examples of scheduler configurations using the ksctl utility. Refer to the CLI or API documentation for details.

Default Schedulers

There are two system-generated schedulers, system_auto_key_rotation and system_auto_user_password_expiry_notification.

Key Rotation Scheduler

The system-generated scheduler system_auto_key_rotation is disabled by default. When this scheduler is enabled, it runs every day at midnight, and rotates the keys with a rotation date less than the current time. To enable the scheduler, run:

ksctl scheduler configs modify key-rotation --id <ID> --disabled=false

**Example**

#!bash
ksctl scheduler configs modify key-rotation --id e08708b9-c6f0-49f2-bbea-64bd6ee80779 --disabled=false

Note

The scheduler that rotates the key (system_auto_key_rotation) based on scheduledRotationDate is one per domain and it comes disabled by default. Therefore, you need to enable this scheduler in relevant domains after migration.

Keys are rotated based on the value configured in the scheduledRotationDate parameter. You can configure this value by setting the rotation-frequency-days parameter during key create or key modify request.

The value of the rotation-frequency-days parameter is defined in number of days, and should be greater than or equal to 0. The value of scheduledRotationDate is calculated based on key creation time + rotation-frequency-days.

When the scheduler runs, it only rotates the keys whose scheduledRotationDate less than the current time.

For example, if rotation-frequency-days is set to 5 days for any key, the scheduler will rotate that key every 5 days.

If rotation-frequency-days is set to "0", the key will not be rotated by the system_auto_key_rotation scheduler. For more details, refer to Configuring Key Rotation Frequency Days.

Syntax (Key create)

ksctl keys create --name <key-name> --rotation-frequency-days <number-of-days>

Syntax (Key modify)

ksctl keys modify --name <key-name> --rotation-frequency-days <number-of-days>

User Password Expiry Notification Scheduler

system_user_password_expiry_notification is enabled by default. It runs every day at midnight, and sends password expiry reminder emails if other conditions are met. Refer to the password policy page for details on these conditions.

Time Specification

The time that a job runs is described in the run-at parameter using the cron expression format: "* * * * *"

These five values indicate when the job should be executed. They are in order of minute, hour, day of month, month, and day of week.

The following table lists the accepted values:

Field NameMandatoryAllowed ValuesAllowed Special Characters
MinuteYes0-59* / , -
HourYes0-23* / , -
Day of monthYes1-31* / , -?
MonthYes1-12 or JAN-DEC* / , -
Day of weekYes0-6 or SUN-SAT* / , -?

Note

Month and Day of week field values are case insensitive. For example, "SUN", "Sun", and "sun" are equally accepted.

Note

Scheduler itself is a generic service, so it provides granularity of a minute. A job configuration should take the nature of operation information into consideration. For example, rotating the same set of multiple keys and backing up a database every minute are highly unlikely use cases.

Allowed Special Characters

The following table describes the use of special characters in the cron expression format:

Special CharacterDescription
Asterisk *Indicate that the cron expression will match for all values of the field. For example, using an asterisk in the 5th field (month) would indicate every month.
Slash /Describe increments of ranges. For example, 3-59/15 in the 1st field (minutes) would indicate the 3rd minute of the hour and every 15 minutes thereafter.
Comma ,Separate items of a list. For example, using "MON,WED,FRI" in the 5th field (day of week) would mean Mondays, Wednesdays, and Fridays.
Hyphen -Define ranges. For example, 9-17 would indicate every hour between 9am and 5pm inclusive, MON-WED would indicate Monday through Wednesday, and JAN-JUN would indicate every month from January through June.
Question mark ?Use instead of "*" for leaving either day-of-month or day-of-week blank. "?" means no specific value. For example, to run the job every 10th day of the month and not limit the job to a particular day of the week: "* * 10 * ?".

Permissions

You require specific group memberships to manage particular job configuration types. As well, you need to be logged into the root domain.

Job ConfigurationRequired GroupRequired Domain
Key rotationKey Admin
System BackupBackup Admin
Domain BackupDomain Backup Admin
User Password Expiry Notificationadmin (application administrators)

Creating Job Configurations

To create a job configuration, run the command ksctl scheduler configs create <operation> --name <config-name> --run-at "<cron-expression-format>".

Here, required values are:

  • <operation>: Operation to schedule. The options are:

    • backup: Create a job configuration for backup operation. Refer to Scheduling Backups for more details and options.

    • key-rotation: Create a job configuration for key rotation. Refer to Scheduling Key Rotation for more details and options.

  • <config-name>: Name for the job configuration.

  • <cron-expression-format>: Time when the job runs. The format must have five fields. If the number of fields is not equal to five, the format becomes invalid. Refer to time specification for details.

Additional required values are specific to the operation.

Viewing Existing Job Configurations

To view the list of job configurations, run the command ksctl scheduler configs list.

Example:

ksctl scheduler configs list
{
  "skip": 0,
  "limit": 10,
  "total": 2,
  "resources": [
    {
      "id": "20c5263d-e296-4994-9129-b71aff49f4b3",
      "uri": "kylo:kylo:scheduler:job_configs:20c5263d-e296-4994-9129-b71aff49f4b3",
      "account": "kylo:kylo:admin:accounts:kylo",
      "application": "ncryptify:gemalto:admin:apps:kylo",
      "devAccount": "ncryptify:gemalto:admin:accounts:gemalto",
      "createdAt": "2020-04-12T06:07:40.054712Z",
      "name": "ab-key-rot-config",
      "updatedAt": "2020-04-12T06:07:40.054712Z",
      "description": "",
      "operation": "key_rotation",
      "run_at": "45 11 * * 0",
      "run_on": "any",
      "disabled": false
    },
    {
      "id": "fd0c27b8-a502-47cc-b6bc-4c1c6fbbe89a",
      "uri": "kylo:kylo:scheduler:job_configs:fd0c27b8-a502-47cc-b6bc-4c1c6fbbe89a",
      "account": "kylo:kylo:admin:accounts:kylo",
      "application": "ncryptify:gemalto:admin:apps:kylo",
      "devAccount": "ncryptify:gemalto:admin:accounts:gemalto",
      "createdAt": "2020-04-12T06:06:15.110531Z",
      "name": "ab-backup-config",
      "updatedAt": "2020-04-12T06:06:15.110531Z",
      "description": "",
      "operation": "database_backup",
      "run_at": "0 12 * * 0",
      "run_on": "any",
      "disabled": false
    }
    ]
}

The output shows existing job configurations.

Viewing Details of Job Configurations

To view the details of a job configuration, run the command ksctl scheduler configs get --id "configID". Here, <configID> represents the ID of the configuration.

Example

ksctl scheduler configs get --id "fd0c27b8-a502-47cc-b6bc-4c1c6fbbe89a"
{
  "id": "fd0c27b8-a502-47cc-b6bc-4c1c6fbbe89a",
  "uri": "kylo:kylo:scheduler:job_configs:fd0c27b8-a502-47cc-b6bc-4c1c6fbbe89a",
  "account": "kylo:kylo:admin:accounts:kylo",
  "application": "ncryptify:gemalto:admin:apps:kylo",
  "devAccount": "ncryptify:gemalto:admin:accounts:gemalto",
  "createdAt": "2020-04-12T06:06:15.110531Z",
  "name": "ab-backup-config",
  "updatedAt": "2020-04-12T06:06:15.110531Z",
  "description": "",
  "operation": "database_backup",
  "run_at": "0 12 * * 0",
  "run_on": "any",
  "disabled": false
}

Modifying Job Configurations

Existing job configurations can be modified when needed. To modify a job configuration, run the command: ksctl scheduler configs modify <operation> --id "<configID>" <args>

Here,

  • <operation>: Operation can be backup or key-rotation.

  • <configID>: ID of the job configuration to be modified.

  • <args>: Parameters to modify.

Example Request 1

ksctl scheduler configs modify key-rotation --id "20c5263d-e296-4994-9129-b71aff49f4b3" --run-at "50 11 * * 0"

Example Response 1

{
  "id": "20c5263d-e296-4994-9129-b71aff49f4b3",
  "uri": "kylo:kylo:scheduler:job_configs:20c5263d-e296-4994-9129-b71aff49f4b3",
  "account": "kylo:kylo:admin:accounts:kylo",
  "application": "ncryptify:gemalto:admin:apps:kylo",
  "devAccount": "ncryptify:gemalto:admin:accounts:gemalto",
  "createdAt": "2020-04-12T06:07:40.054712Z",
  "name": "ab-key-rot-config",
  "updatedAt": "2020-04-12T06:14:57.23658004Z",
  "description": "",
  "operation": "key_rotation",
  "run_at": "50 11 * * 0",
  "run_on": "any",
  "disabled": false
}

Example Request 2 (update replaced-key-state value from Deactivated to ProtectStop)

ksctl scheduler configs modify key-rotation --id d0c48426-f5cc-416b-b935-e91b5872db8a --replaced-key-state "ProtectStop"

Example Response 2

{
    "id": "d0c48426-f5cc-416b-b935-e91b5872db8a",
    "uri": "kylo:kylo:scheduler:job_configs:d0c48426-f5cc-416b-b935-e91b5872db8a",
    "account": "kylo:kylo:admin:accounts:kylo",
    "application": "ncryptify:gemalto:admin:apps:kylo",
    "devAccount": "ncryptify:gemalto:admin:accounts:gemalto",
    "createdAt": "2023-04-27T04:39:57.84822Z",
    "name": "test2",
    "updatedAt": "2023-04-27T04:52:36.182154615Z",
    "description": "",
    "operation": "key_rotation",
    "run_at": "0 1 * * *",
    "run_on": "any",
    "disabled": false,
    "job_config_params": {
        "change_state_after_time": 3,
        "replaced_key_state": "ProtectStop"
    }
}

Example Request 3 (update change-state-after-time to some valid value(>=0))

ksctl scheduler configs modify key-rotation --id d0c48426-f5cc-416b-b935-e91b5872db8a --change-state-after-time 10

Example Response 3

{
    "id": "d0c48426-f5cc-416b-b935-e91b5872db8a",
    "uri": "kylo:kylo:scheduler:job_configs:d0c48426-f5cc-416b-b935-e91b5872db8a",
    "account": "kylo:kylo:admin:accounts:kylo",
    "application": "ncryptify:gemalto:admin:apps:kylo",
    "devAccount": "ncryptify:gemalto:admin:accounts:gemalto",
    "createdAt": "2023-04-27T04:39:57.84822Z",
    "name": "test2",
    "updatedAt": "2023-04-27T04:58:36.855601961Z",
    "description": "",
    "operation": "key_rotation",
    "run_at": "0 1 * * *",
    "run_on": "any",
    "disabled": false,
    "job_config_params": {
        "change_state_after_time": 10,
        "replaced_key_state": "Deactivated"
    }
}

Manually Running Job Configurations

A scheduled configuration can be run manually when needed. To manually run a job configuration, run the command: ksctl scheduler configs run-now --id "<configID>"

Here, <configID> represents the ID of the configuration. The command creates a new job and waits for the job to be posted on the job queue. The "job_id" is returned if the job is posted within about 30 seconds.

Example:

ksctl scheduler configs run-now --id "e90cb2df-7df5-487a-ab5e-2c0ead7405c4"
{
  "job_id": "1e05dfb0-a5f9-48f6-afdf-406c368d2847",
  "job_config_id": "e90cb2df-7df5-487a-ab5e-2c0ead7405c4"
}

Disabling Job Configurations

You can disable an existing job configuration to temporarily prevent future job runs. To disable job configuration, run the command: ksctl scheduler configs modify <operation> --id "<configID>" --disabled

Here,

  • <operation>: Operation can be backup,key-rotation, or user-password-expiry-notification.

  • <configID>: ID of the job configuration to be modified.

  • disabled: A boolean value indicated whether the job configuration is disabled, and will not run in the future.

Example Request

ksctl scheduler configs modify user-expiry-notification --id "20c5263d-e296-4994-9129-b71aff49f4b3" --disabled

Example Response

{
  "id": "20c5263d-e296-4994-9129-b71aff49f4b3",
  "uri": "kylo:kylo:scheduler:job_configs:20c5263d-e296-4994-9129-b71aff49f4b3",
  "account": "kylo:kylo:admin:accounts:kylo",
  "application": "ncryptify:gemalto:admin:apps:kylo",
  "devAccount": "ncryptify:gemalto:admin:accounts:gemalto",
  "createdAt": "2020-04-12T06:07:40.054712Z",
  "name": "ab-key-rot-config",
  "updatedAt": "2020-04-12T06:14:57.23658004Z",
  "description": "",
  "operation": "key_rotation",
  "run_at": "50 11 * * 0",
  "run_on": "any",
  "disabled": true
}

To enable a disabled job configuration, run the command: ksctl scheduler configs modify <operation> --id "<configID>" --disabled=false

Example Request

ksctl scheduler configs modify user-password-expiry-notification --id "20c5263d-e296-4994-9129-b71aff49f4b3" --disabled=false

Deleting Job Configurations

Caution

This is a permanent operation. If you wish to temporarily suspend a scheduled job, you can disable it instead.

To delete a job configuration, run the command ksctl scheduler configs delete --id "<configID>". Here, <configID> is the ID of the job configuration to be deleted. The specified job configuration is deleted without any message.

After a configuration is deleted, it will no longer run jobs automatically.

Job Runs

A job is created and run automatically when a scheduler configuration is run manually (using run-now) or automatically at a schedule defined in the job configuration. You can view the results of jobs executed in the past, including status and error count.

Viewing Job Runs

To view the list of already run jobs for the logged in account, run the command ksctl scheduler jobs list.

Example:

ksctl scheduler jobs list
{
  "skip": 0,
  "limit": 10,
  "total": 2,
  "resources": [
    {
      "id": "5ce37ebd-f43f-4a97-bbaf-d6a7416074a7",
      "uri": "kylo:kylo:scheduler:jobs:5ce37ebd-f43f-4a97-bbaf-d6a7416074a7",
      "account": "kylo:kylo:admin:accounts:kylo",
      "application": "ncryptify:gemalto:admin:apps:kylo",
      "devAccount": "ncryptify:gemalto:admin:accounts:gemalto",
      "createdAt": "2020-04-15T02:25:01.749924Z",
      "name": "rotate AES keys weekly",
      "updatedAt": "2020-04-15T02:25:14.003393Z",
      "job_config_id": "cbf85c25-08e9-4932-93da-a1042aafafdd",
      "description": "This is to rotate AES keys every Sunday, at 02:00",
      "operation": "key_rotation",
      "job_config_params": {
        "meta": {
          "naeState": "Restricted"
          },
        "query": {
          "algorithm": "AES"
          },
          "deactivate_replaced_key": 30
          },
      "enqueued_at": "2020-04-15T02:25:01.749791Z",
      "status": "completed",
      "processing_node": "local-node",
      "details": {
        "job_id": "5ce37ebd-f43f-4a97-bbaf-d6a7416074a7",
        "job_config_id": "cbf85c25-08e9-4932-93da-a1042aafafdd",
        "name": "rotate AES keys weekly",
        "operation": "key_rotation",
        "status": "completed",
        "percent_done": 100,
        "details": {
          num_rotated": 1
        }
      }
    },
    {
      "id": "5f2cf5fb-94ef-419a-9cf6-4f4045d43dc1",
      "uri": "kylo:kylo:scheduler:jobs:5f2cf5fb-94ef-419a-9cf6-4f4045d43dc1",
      "account": "kylo:kylo:admin:accounts:kylo",
      "application": "ncryptify:gemalto:admin:apps:kylo",
      "devAccount": "ncryptify:gemalto:admin:accounts:gemalto",
      "createdAt": "2020-04-15T02:09:02.740656Z",
      "name": "rotate AES keys",
      "updatedAt": "2020-04-15T02:09:13.978049Z",
      "job_config_id": "61bf1c6f-f1b7-4ef9-b097-af8304647ecf",
      "description": "This is to rotate AES keys",
      "operation": "key_rotation",
      "job_config_params": {
        "meta": {
          "naeState": "Restricted"
          },
        "query": {
          "algorithm": "AES"
          },
        "deactivate_replaced_key": 30
        },
      "enqueued_at": "2020-04-15T02:09:02.740554Z",
      "status": "completed",
      "processing_node": "local-node",
      "details": {
        "job_id": "5f2cf5fb-94ef-419a-9cf6-4f4045d43dc1",
        "job_config_id": "61bf1c6f-f1b7-4ef9-b097-af8304647ecf",
        "name": "rotate AES keys",
        "operation": "key_rotation",
        "status": "completed",
        "percent_done": 100,
        "details": {
          "num_rotated": 1
        }
      }
    }
  ]
}

The output shows that two jobs have run successfully.

Viewing Details of a Particular Job Run

To view the details of a particular job run for the logged in account, run the command ksctl scheduler jobs get --id. Here, --id is the ID of the job run you are searching for.

Example:

ksctl scheduler jobs get --id "5f2cf5fb-94ef-419a-9cf6-4f4045d43dc1"
{
  "id": "5f2cf5fb-94ef-419a-9cf6-4f4045d43dc1",
  "uri": "kylo:kylo:scheduler:jobs:5f2cf5fb-94ef-419a-9cf6-4f4045d43dc1",
  "account": "kylo:kylo:admin:accounts:kylo",
  "application": "ncryptify:gemalto:admin:apps:kylo",
  "devAccount": "ncryptify:gemalto:admin:accounts:gemalto",
  "createdAt": "2020-04-15T02:09:02.740656Z",
  "name": "rotate AES keys",
  "updatedAt": "2020-04-15T02:09:13.978049Z",
  "job_config_id": "61bf1c6f-f1b7-4ef9-b097-af8304647ecf",
  "description": "This is to rotate AES keys",
  "operation": "key_rotation",
  "job_config_params": {
    "meta": {
      "naeState": "Restricted"
      },
    "query": {
      "algorithm": "AES"
      },
    "deactivate_replaced_key": 30
    },
  "enqueued_at": "2020-04-15T02:09:02.740554Z",
  "status": "completed",
  "processing_node": "local-node",
  "details": {
    "job_id": "5f2cf5fb-94ef-419a-9cf6-4f4045d43dc1",
    "job_config_id": "61bf1c6f-f1b7-4ef9-b097-af8304647ecf",
    "name": "rotate AES keys",
    "operation": "key_rotation",
    "status": "completed",
    "percent_done": 100,
    "details": {
      "num_rotated": 1
    }
  }
}

Deleting a Job

To delete a job, run the command ksctl scheduler jobs delete --id. This command stops the job (if it is running) and deletes it without any confirmation message.

On this page