AIP Console is designed to support one customer only
It is not possible to manage multiple customers in the same AIP console for now. If you need to deploy multiple AIP Consoles, you will need to adapt the strategy of your infrastructure. AIP Console supports multiple AIP Console Front Ends on the same machine. AIP Console supports multiple analysis nodes (the analysis node is an "image" that runs the AIP Node (Back End server) and contains the AIP installation and its running environment (runtimes, program/log/temp folders….etc). There is no feature to monitor the performance of multiple AIP Consoles (parallel analysis, jobs...) on the same machine. This task will need to be supported by the customer.
Compatibility with CAST AIP
- AIP Console is currently compatible with CAST AIP ≥ 8.3.6. If you want to use AIP Console and you are using an unsupported release of CAST AIP, you will need to either upgrade to a compatible release of CAST AIP, or install a compatible release of CAST AIP from scratch.
- CAST recommends the most recent release of CAST AIP to take full advantage of all available features.
AIP Console doesn't support a scheduler feature
To plan scans automatically on a set of applications, this feature needs to be implemented outside of the AIP Console.
AIP Console doesn't support source code extraction automation
AIP Console's current role is limited to receiving source code and then starting the scanning process. There is no feature to automate source code extraction.
No equivalent of CAST Management Studio Content Enrichment tools
CAST Management Studio contains various "content enrichment tools" such as tools to run SQL queries during an Analysis, Universal Importer mechanism, Reference Pattern tools etc. and these tools are not available in AIP Console. The workaround is to use extensions wherever possible. For example, there is no Reference Pattern feature in AIP Console, but you can manage it with an extension.
- one Content Enrichment tool has been implemented: Update KB Assistant.
- if you import an application from CAST Management Studio, then any Content Enrichment tool present in the Application will now also be visible in AIP Console, but with the exception of the Update KB Assistant tool, the tools will be read-only.
No ability to manage Dynamic Links in the GUI
Note that it is currently not possible to manage DLM in the GUI and DLM.XML files can be uploaded to bulk manage Dynamic Links (in AIP Console v. ≥ 1.19 this feature has been implemented - see Application - Config - Summary of Dynamic Links).
AIP Console does not support all technologies already supported by legacy CAST AIP deployments
The following technologies cannot currently be analyzed with CAST AIP Console:
- Visual Basic (supported from v. ≥ 1.23)
- Custom/User Community extensions using Universal Importer technology
No central user rights between AIP Console and Dashboards
Even though it is possible to configure SSO (Single Sign On) for the AIP Console and for the CAST dashboards, there is no configuration GUI available in AIP Console to manage roles and authorization for the embedded Dashboards. This is something that must be done manually.
No interface for embedded Dashboard configuration
Currently, some manual steps are still required to deploy embedded dashboards.
No certification for secure deployment
AIP Console will need to evolve after GA to support a fully secure architecture.
No Transaction viewer like in Transaction Configuration Center
There is no way to display the call graph of a transaction to get an overview (in AIP Console v. ≥ 1.15 this feature has been implemented - see Application - Transactions - Call Graph).
Application backups do not include Objectives
When an Application backup is run, the resulting backup does not record any selections made in the Objectives step of the delivery wizard. This means that any customizations made in this step will not be backed up and will not be restored. As a direct consequence, for example, enabling the Security Assessment objective will also enable Security Dataflow. When an application is restored, since the Objectives are not backed up, the Security Dataflow options will return to their default position - disabled (in AIP Console v. ≥ 1.22 this feature has been implemented - see Administration Center - Applications - Application Details).
ZIP files containing files with non-standard characters in the file name
If your source code contains files with non-standard characters in the file name, such as é à ä etc. you must ensure that the the ZIP file has been created with a packaging tool that enforces the use of UTF-8 encoding for the names of the files within the ZIP. For example, the file names within ZIPs created with 7zip are encoded (by default) using Code page 437, and this will cause an exception when the ZIP file is uploaded to AIP Console during the source code delivery process. One workaround is to force the packaging tool to use UTF-8 encoding - for example this can be achieved using 7zip by adding the parameters "cu" to the parameters field: