Home
Reference
Review reference information for the product.
AppScan® Source command line interface (CLI)
The CLI is an interface to core AppScan® Source functionality.
AppScan® Source command line interface (CLI) commands
login_file

Reference
Review reference information for the product.
- The Ounce/Make build utility
  Ounce/Make is a tool that automates the importing of configuration information into AppScan® Source from build environments that use makefile. Ounce/Make eliminates the need to import configuration information from makefiles manually; this the recommended method of configuring these projects.
- AppScan® Source command line interface (CLI)
  The CLI is an interface to core AppScan® Source functionality.
  - Objects and context
  - AppScan® Source command line interface (CLI) permissions
    Many CLI commands require that you have the appropriate AppScan® Source permissions.
  - Starting the AppScan® Source command line interface (CLI)
  - Command syntax
    AppScan® Source command line interface (CLI) commands conform to a usage template with required and optional arguments, similar to a command shell. CLI commands are not case sensitive and do not require switches for different arguments.
  - AppScan® Source command line interface (CLI) commands
    - AppScan® Source command line interface (CLI) command summary
    - about (a)
    - clearcache (cc)
    - delete (del)
    - deleteassess (da)
    - deleteuser (du)
    - delvar (dv)
    - details (det)
    - echo
    - getaseinfo (gase)
    - help (?)
    - import (im)
    - info (i)
    - list (ls, dir)
    - listassess (la)
    - listgroups (lgrp)
    - listusers (lu)
    - log
    - login (in)
    - login_file
    - login_local (local)
    - logout (out)
    - moduser (mu)
    - newuser (nu)
    - openapplication (oa)
    - openassessmentfile (oaf)
    - password (passwd)
    - printuser (pu)
    - publishassess (pa)
    - publishassessase (pase)
    - quit
    - record (rc)
    - refresh (rf)
    - register (reg)
    - removeassess (da)
    - report (rpt)
    - scan (sc)
    - script (scr)
    - setaseinfo (sase)
      If your AppScan® Enterprise Server has been installed with the AppScan Enterprise Console option, you can publish assessments to it. The Enterprise Console offers a variety of tools for working with your assessments - such as reporting features, issue management, trend analysis, and dashboards.
    - setcurrentobject (set, cd)
    - setvar (sv)
    - unregister (unreg)
  - Running automated assessments
    The AppScan® Source command line interface (CLI) enables you to automatically import an AppScan Source project file (.ppf) and scan your source code. From the command line, you can run a script, such as the following sample, Run_Assessments.txt.
- The Ounce/Ant build tool
  This section describes how to use Ounce/Ant, an AppScan® Source build utility that integrates AppScan Source and Apache Ant. Integrating Ounce/Ant with your Ant environment helps you automate builds and code assessments.
- AppScan® Source Data Access API
  The Data Access API provides access to AppScan® Source-generated assessment results, including findings and finding details. It also provides access to assessment metrics such as analysis date and time, lines of code, V-density, and number of findings.
- Glossary
  Learn common product terminology.

`login_file`

Description

Log in to the AppScan® Enterprise Server using a token file (token files are created using the -persist option with the CLI login (in) command or when creating the AppScan® Source for Automation user).

If the login is successful, the prompt changes to AllApplications>> to indicate that you are logged in.

Syntax

login_file server token_file [-acceptssl]

server: Required. Specify the URL for your Enterprise Server instance.
token_file: Required. Indicate the path and file name of the token file. If the token file was created with the CLI login (in) command, the file is ouncecli.token and it resides in the .ounce folder of the users home directory. If the token file was created for AppScan® Source for Automation, the file is <data_dir>/config/ounceautod.token (where <data_dir> is the location of your AppScan® Source program data, as described in Installation and user data file locations).
-acceptssl: Optional. Automatically accept SSL certificates. For more information, see AppScan Enterprise Server SSL certificates
Important: If this argument is not included, logging in or publishing to the AppScan® Enterprise Console will fail with error if an invalid certificate is encountered (if you have not already permanently accepted the certificate while logging in via another AppScan® Source client product).

Example

User John Smith logs into the AppScan® Enterprise Server, using a token file that was created on Windows™ from the CLI:

>> login_file https://myserver:9443/ase/ 
     C:\Users\Administrator\.ounce\ouncecli.token
Login successful.
AllApplications>>