-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PM-14627] totp secret is assigned to cipher object in zohovalut-csv-importer to… #11912
base: main
Are you sure you want to change the base?
Conversation
… populate when importing keys from zoho vault fixes bitwarden#11872 closes bitwarden#11872
Thank you for your contribution! We've added this to our internal Community PR board for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kshashikumar Thank you for your contribution 🚀
Your changes are looking good. I just tested and you can actually simply assign the full login_totp
to cipher.login.totp
. This has the benefit of retaining all information (secret, algorithm and period)
Would you be willing to also add unit tests for this or even for the full zohovalut-csv-importer?
Unfortunately this specific importer has no unit tests yet, but examples can be found within libs/importer/spec.
Kind regards,
Daniel
Thank you for the review @djsmith85, will update the cipher.login.totp to take full url and also will add unit tests for it. Thanks again |
…ts for zohovault importer
Hi @djsmith85 , updated cipher.login.totp to take full totp url and also implemented unit tests for above. Please let me know if any further changes needed. Thank you for your time and consideration. |
… populate when importing keys from zoho vault fixes #11872 closes #11872
🎟️ Tracking
📔 Objective
totp secret is assigned to cipher object in zohovalut-csv-importer to populate when importing keys from zoho vault fixes #11872 closes #11872
📸 Screenshots
Before
After
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes