Sensitive data
Data is provided during an install, update, modify, roll back, or uninstall process that must be protected. Sensitive data is not stored in the installRegistry.xml and the installed.xml files. Packages determine which data is sensitive. An example of sensitive data is credentials like a user name and a package If we provide sensitive data after starting Installation Manager, the sensitive data is available to all packages until you exit Installation Manager.For data that is not marked sensitive, information is encrypted and stored in the installRegistry.xml and the installed.xml files. The data is encrypted with a default encryption key. We can use the -passwordKey option to change the default encrypt passwords to make the data more difficult, but not impossible, to decrypt.
The installRegistry.xml and the installed.xml files are in the agent data directory.
Examples
For these examples, Package A and Package B are in a repository that requires authentication. We must provide credentials to access this repository.
- We start Installation Manager in wizard mode. During the installation of Package A, we provide our credentials to access the repository. After the installation completes, we update Package B. Package B can use the credentials that we provided during the installation of Package A. After you exit Installation Manager, our credentials are no longer available.
- We start Installation Manager in wizard mode. During the installation of Package A, we provide our credentials. After the installation completes, you exit Installation Manager. Next, you start Installation Manager and install Package B. The credentials that we provided during the installation of Package A are not available. We must provide our credentials to install Package B.
- We start Installation Manager to uninstall Package A. We must provide our credentials for the uninstall process.
Home