*Goal:*
As an admin I want to distribute a library from one server to another without needing to go though all the data sources and retype their passwords.
*Details:*
Since the passwords are not exported prompting during import or scripting could be solutions. Prompting would at least help the cases where you forget to set password on seldom used data sources hidden deep in the structure.
The nicest thing would be in the bootstrap encryption password could be used (and the encrypted passwords are exported) and if the same encryption password is used on the TSS where the library export is imported, the encrypted passwords could be reused.
Bumping this one, and also commenting that I don't really want a solution where the encryption key has to be the same in both libraries. I'd ideally like to see the export-library-content command updated with a couple of extra options - e.g. '--include-plain-passwords' and '--include-passwords' - that way we'd have the option to include the passwords in plain text or encrypted (perhaps allow a specific encryption key to be provided in the command line as well?)