(Migrated from https://github.com/syndesisio/syndesis/issues/3423)
Author: Zoran Regvart
[!-- Check ONLY one of the following options with "x" --]
[x] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report [!-- Please search GitHub for a similar issue or PR before submitting --]
[ ] Documentation issue or request
[!-- If possible, please choose the appropriate labels for your issue. You find a description of all
labels used at https://doc.syndesis.io/#dev-labels --]
Briefly describe the issue you are experiencing (or the feature you want to see implemented on Syndesis).
+ For BUGS, tell us what you were trying to do and what happened instead.
+ For NEW FEATURES, describe the User Persona demanding it and its use case.
We're recurringly stumbling with managing imports/exports of integrations containing secrets (e.g. passwords for database connection). Perhaps we should rethink our approach. Perhaps it would be better to prompt the user for export password and re-encrypt the secret content with that export password that'll also be needed when importing the integration.
[!-- Describe what the desired behavior would be, enlistin gthe acceptance criteria. --]
No more reports like #3404 #2603 #2602 #2585
For features/bugs tackling with UI functionality, drag and drop a screenshot depicting the desired presentation layer or supporting the UX narrative for the new functionality.
Enlist all the acceptance criteria for new features or the steps required to reproduce the bug/regression reported.
1. On export prompt for a password, decrypt secrets with instance key and re-encrypt with given password
2. On import prompt for a password, decrypt secrets with given password and re-encrypt with instance key