Skip to main content

CI/CD Dashboard Credential Encryption

ThisCredential functionalityencryption for CI/CD dashboards protects sensitive values used by automation. Treat this page as security-sensitive guidance: never paste real passwords, tokens, keys, or decrypted values into documentation, tickets, chat, or screenshots.

  • Store secrets in approved secret managers or CI/CD credential stores.
  • Encrypt values before they are committed or shared with deployment artifacts.
  • Limit decryption capability to the runtime or owner that actually needs it.
  • Rotate credentials when ownership, access scope, or exposure risk changes.
  • Audit who can view, edit, or deploy encrypted dashboard configuration.

Validation checklist

  1. Confirm the dashboard can read encrypted values at runtime.
  2. Confirm logs do not print decrypted credentials.
  3. Test failure behavior when a credential is tomissing, encryptexpired, credentialsor filesrevoked.
  4. Document used for both CICD’s (s3rotation and git)emergency .revocation

    Plain Text Files

    steps.

    controller.json (template)

    {
        "controller": {
            "url": "http://<replace_IP>:8080",
            "instances": ["<replace_instanceID>"],
            "ec2Creds": "ec2.creds",
            "timeOut": 180,
            "username": "<replace_username>",
            "password": "<replace_password>",
            "workFolder": "<replace_path/to/AIQ/resources>"
        }
    }

    githttp.json (template)

    {
        "username": "<replace_username>",
        "password": "<replace_password>",
        "repository": "http://<replace_url_to_repository>.git",
        "branch": "<replace_branch>",
        "sshPhrase": "",
        "sshKey": ""
    }

    ec2creds.creds (template)

    AWS_ACCESS_KEY_ID=<replace_awsKEYIDE>
    AWS_SECRET_ACCESS_KEY=<replace_awsSecretAccessKey>

    AIQ - Encryption UI

    Under Global Options | Preferences

    Git Credentials

    Click open to load the Git creds file

    Click save to encrypt the file

    gitHttp.json (encrypted)

    VCgam99C3GHqwOb/UoxxRJv92Q+kIGAq9/wegy8PX5IgQfO5bDmA/SkGB6Ybv4AG/O6MVVj+g5a6rOS8DNx661SA5cs2AAc2yLuWaZTljZ0RAvNhEzZVCg7Zr7HeMy867hhPGjXOnx+0+CnFswh3BK4slK8cLkNpKobOyKn6kusubZLtUV5fxKZN5+nj3VepsFTyh7+XQ3JQqYRghXaSFBhLSHiZCtvSyN2eAbEmIW8=


    Ec2 Credentials

    Click open to load the ec2 creds file

    Click save to encrypt the file

    ec2creds.creds (encrypted)

    84zVbQScFoJikfiR4mLwKiUzmUFnX10g9lT9R1hJtRFouXBrS9vIUdYZpqA0cy8l0t93OMa/Mt7egmCnBaXKdPRVxmPVu2Y4wZgvzkLZb5MlPQIgUIc0OAqo9pdiGvR1VaUgal5rO7CSoIwkL/u2hR4nTVDs3j0lcRc6L0L2fKU=


    AIQ Credentials

    Click open to load the AIQ creds file

    Click save to encrypt the file

    the Work Folder field is optional on recent releases, and it will be removed soon from this page.

    AIQ creds (encrypted)

    etr9LYZBcK7r2eBsp/O98enfcdiTk/wx8UzqS7eOQeiOxB2qMkjYaanuhg35jcHjII+CXHbt8SB7hwW4WfY3yp0EtMhcSqtQqbNuVJ6HFY1z0j36no/fhZeRooCNte58MDLZTPOXr8UaH9MHc5yW0bQR1olrcRmEQ6CeFJ6AoCC5x6Sz0k/bpf6j8pVzZh4/afZqQqoJ4NAJJNlWZppVwBI3hOVhY5Zg41aKRDjmA/seoBOtVgWkACe4WT5h0L3SfwFTzOhn2JudDFTslDcODw==

    Setting properties into the build.xml

    Using CICD GIT

    <property name="gitCredentials" value="githttp.json" />

    Access to AIQ

    <property name="aiqCreds" value="creds.json" />

    Using CICD s3

    <property name="awsCredentials" value="ec2.creds" />

    CICD Git ( clone and push to repository)

    <taskdef name="downloadRepository" classname="com.appvance.ci.git.DownloadRepository">	<classpath refid="RestClientLibPath" /></taskdef><downloadRepository folder="${localEmpyFolder}" credentials="${gitCredentials}" />			
    < ....... Methods to run scenarios, Goes here .......>	
    <taskdef name="commitReports" classname="com.appvance.ci.git.UploadRepository">	<classpath refid="RestClientLibPath" /></taskdef><commitReports 
    <credentials="${gitCredentials}" folder="${localEmpyFolder}" customer="${customer}" /> 

    Last updated: MarchOctober 25,6, 20242026

    If you have any feedback on this topic, please contact us at documentation@appvance.ai