Technical lineage password manager integration design

Warning The CLI lineage harvester is now deprecated and will officially reach its end-of-life on July 31, 2026. To ensure a smooth transition, we encourage you to begin creating technical lineage via Edge, if you haven't already.

When you run the lineage harvester, you can either:

This topic provides guidance on how to structure the JSON file and which commands to use, to store the passwords locally in your password manager.

Structure of the JSON file

If you prepare a JSON file with your passwords, you have to name the file passwords.json.

The JSON file must have two sections:

The JSON file must have the following structure:

{
 "catalogs": [
  {
   "url" : "<url-to-collibra-cloud>", 
   "username":"<username-to-sign-in-to-collibra>",
   "password": "<password-to-sign-in-to-collibra>"
  }
 ],
 "sources": [
  {
   "id": "<id-of-your-database>",
   "username": "<database-username>",
   "password": "<database-password>"
  }
 ]
}

Examples of commands

When you run the lineage harvester, you can use one of the following commands to provide the passwords:

Passwords location

Command

a locally stored JSON file cat passwords.json | ./bin/lineage-harvester full-sync --passwords-stdin
a custom script, for example from a password manager <prepare-passwords-command> | ./bin/lineage-harvester full-sync --passwords-stdin

Note Depending on your password manager, you may need different parameters. For example, see the LastPass documentation for the parameters needed by LastPass.