Generate tokens for individual users

Prerequisite

You must be a registered customer administrator.

To create an access token for a specified user:

  1. In the command prompt, navigate to the path where fcli is extracted.

  2. (Optional) View the various administrator and user operations available.

    Copy 
    fcli aviator -h

     

    Argument Description
    -h, --help Shows the help message and exits.
    admin-config Manages the SAST Aviator administrator configurations (start here).
    session Manages the SAST Aviator user sessions (start here).
    entitlement Manages the SAST Aviator entitlements.
    app Manages the SAST Aviator applications.
    ssc Use SAST Aviator with SSC.
    token Manage SAST Aviator access tokens.
    Note: Use admin-config to view entitlement, manage applications, and generate tokens and session to audit.
    Ensure to create an admin-config before performing administrator tasks and a user session before auditing.

  3. Create an administrator configuration for interacting with SAST Aviator.

    Copy 
    fcli aviator admin-config create --url <aviator_server_url> --tenant <tenant_name> --private-key <path_to_private_key.pem>
                    

     

    Note: The --private-key can be the file containing the key or the key itself. Ensure the key is in PEM format.

    Optional argument Description Default value
    --admin-config Name of the Aviator administrator configuration. default

    An admin session is created.

  4. Generate the user access token.

    Copy 
    fcli aviator token create --email <admin_email_id> --name <custom_token_name> --save-token <output_file>

     

    Optional arguments Description Default value
    --save-token Save the generated raw token string to the specified file. By default, the string is in json format. NA
    -o, --output Specify the token format. The available formats are csv, table, expr, json, xml, and yaml. NA
    --to-file Specify a file to save the output. NA
    --end-date Specify the token expiration date in YYYY-MM-DD format. 30 days from the date of creation.

     

    Note: OpenText recommends using --save-token optional argument to ease the user experience when using the access token.