Description

This page outlines the issue encountered when we try to configure our credentials to connect to the server for extraction on DMT.
The below image shows the option where we configure the credentials for Team Foundation Server.

The issue is encountered when we try to save the password on the local for more than one application delivered through the same DMT.
The scenario is as follows where we try to deliver Application 1 and Application using the same DMT:

Application A:
- Add Application A through AIC Portal
- Launch DMT
- Add version, choose package TFS and choose Local for Remember password and configure the credentials
- Package and Deliver

Application B:
- Add Application B through AIC Portal
- Launch DMT
- Add version, choose package TFS and choose Local for Remember password and configure the credentials
- Package and Deliver

Now, open DMT for App1, see that the password field is blank, so what was configured is lost.


This is a functional bug where the local storage of the passwords works only in a single application scenario from a single AICPortal or CAST-MS.
In cases where we are using multiple applications from same AIC Portal or CAST-MS, the password is not saved at all.
The localpswds.dat file which stores all the password ,is located under the data folder, which is the root of all the application folders.

Observed in CAST AIP
Release
Yes/No
8.0.x (tick) 
7.3.x(tick)
7.2.x(tick)
7.0.x(error)
Observed on RDBMS
This section is not applicable for this page(DMT)

 

RDBMS
Yes/No
Oracle ServerNA
Microsoft SQL ServerNA
CSS2NA
CSS1NA
Step by Step Scenario
 Application A:

- Add Application A through AIC Portal
- Launch DMT
- Add version, choose package TFS and choose Local for Remember password and configure the credentials
- Package and Deliver

Application B:
- Add Application B through AIC Portal
- Launch DMT
- Add version, choose package TFS and choose Local for Remember password and configure the credentials
- Package and Deliver

Now, open DMT for App1, see that the password field is blank, so what was configured is lost.
Action Plan

 The only solution is to use the other two options available:

  • Not stored : this will not store the password
  • Server : this will save the password on the server files


  1. If you wish to automate DMT, you will need to save the password, hence the option to save on "Server" should be used.
    When you choose to save the password on server, the password is stored in

    %AppData%\Local\CAST\CAST\DMT<AIC-Portal Specific Folder>\data<Application folder(App_id)>{06e97fb2-3e4c-47fa-ae6b-7f7de4bc4728}(version_id)\c118961b-37dc-4198-8195-6e4facfb3488.entity.xml 
    
    in tag like shown below:
    <credentials>
    <delivery.Credentials entry="uuid:b9cc6167-8ace-4b1d-8f53-abdebd457272" loginName="system" storedPassword="CRYPTED2:3FE5B3676B861218F6C339CFEFC9367B" rememberPassword="delivery.Server"/>
    </credentials>


    The above file can be used to automate the DMT in cases when saving password on the local does not work.

  2. Refer to Delivery Manager Tool - Information - DELIVERY Folder Structure and Contents to know which Application and Version id to use.
Impact on Analysis Results and Dashboard


Notes/comments