CRYPTOZ Class |CRYPTOZ Permissions Required - CRYPTOZ Permissions Required - Call-Level Interface Version 2

Teradata® Call-Level Interface Version 2 Reference for Workstation-Attached Systems - 20.00

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Call-Level Interface Version 2
Release Number
20.00
Published
January 2024
Language
English (United States)
Last Update
2024-05-14
dita:mapPath
bmn1691484839905.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
fvz1470444150352
Product Category
Teradata Tools and Utilities

Consider the following two roles with respect to CRYPTOZ permissions.

  • Security officer: Role of the user who is creating and configuring the PKCS#11 token for Identity Token Support. Permissions for the security officer role should include SO.TERADATA.TTU.PKCS11.TOKEN (control).
  • User: Role the users who will be using Identity Token Support. Permissions for the user role should include USER.TERADATA.TTU.PKCS11.TOKEN (read).
Teradata’s TRDGTOKN setup and configuration program requires these permissions by program function:
  • LIST
    • USER.TERADATA.TTU.PKCS11.TOKEN (read)
  • DELETE
    • SO.TERADATA.TTU.PKCS11.TOKEN (update)
  • CREATE
    • SO.TERADATA.TTU.PKCS11.TOKEN (control)