Technical lineage password manager integration design

If you don't want the lineage harvester to store your passwords, you can store them in your password manager. As a result, when you run the lineage harvester, you provide your passwords in a prescribed JSON structure via stdin.

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 "catalogs" section defines the connection information and credentials to your Collibra Data Intelligence Cloud instance.
• The "sources" section defines the connection information and credentials to your data sources. You use the same "id" as the id property in the lineage harvester configuration file.

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.