Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • CTA CTA
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 130
    • Issues 130
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ctacta
  • CTACTA
  • Issues
  • #138
Closed
Open
Issue created Sep 02, 2022 by Joao Afonso@afonsoOwner

Modify the cta-get-encryption-key script to accept the encryption key ID directly from the Tape Server

Introduction

At the moment, the script cta-get-encryption-key queries cta-admin (whish interacts with the ctafrontend) to query for the encryption Key ID. As mentioned in https://gitlab.cern.ch/cta/operations/-/issues/839, this dependency on the ctafrontend can cause some HA related problems.

Fortunately, we can simplify bypass this check - simplify the script a lot - by passing the Key ID directly from the Tape Server. The Tape Server has access to the catalogue, therefore there is no reason not to get this field there.

Task

The cta-get-encryption-key scrpitp needs to be modified to accept the Key ID from the Tape Server and directly use it to obtain the Encryption Key, without using cta-admin command.

As a consequence, it will no longer need to use cta-admin directly, which completely removes the need to interact with the CTA frontend.

As part of this issue, we need to discuss how the new value will be received by the script (and distinguished from a VID).

Edited Sep 02, 2022 by Joao Afonso
Assignee
Assign to
Time tracking