-
-
Notifications
You must be signed in to change notification settings - Fork 435
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
[MIG][16.0] Migration of vault #611
Conversation
Thanks for the migration. Can you please leave this one only for the module |
Fix website in manifest Run pre-commit Move models to own files. Apply OCA conventions Remove logging causing the tests to fail Add application icon Split models into files. Use lambda for defaults Add icon to menuitem Use lambda as suggested Add missing keepass lib Show information if user lacks public key Add note about no https Fix domain for user_id in send wizard. Add permanent note to wizard
vault_controller
…lect all possible users due to access rights - Disable the features if browser isn't using a secure context (https/localhost) - Load required assets in inbox and share frontends - Allow the user to switch a parent of an entry within the same vault - Allow to create entries for vaults using the main menu Entries - Fix bug that encrypted a share twice due to multiple extension with VaultAbstract - Fix a bug on share create that throws a warning about changed values
…changed Note about disaster recovery project Add missing dependency to base_setup for res.config.settings view
Before the path if we create a new child entry from other entry, the complte_name of the entry is not changing when we save the new entry. Doing this changes, we are getting the complete_name correctly. TT38729
vault: Searchpanel improvements: - Add a domain to only show records with children. - Set limit to False. TT38731 vault: Add Vaults to searchpanel view. TT38731
…he fields and files aren't overwritten
… Re-encrypt vaults if the user changes the private key - Recompute access. Unittests
I was able to reproduce the issue. Seems like a hidden bug in all versions. I reproduced it by clicking away the first password dialog when I clean all browser caches. If I try to read |
In my tests I had the issue that the key in vault.right wasn't generated correctly because of the if in the controller. I suspect that this is also the issue for your case. Not 100% sure because the right was marked red in my case but isn't in your case. |
@bosd I can't reproduce it and every button is working. Maybe a module update gone wrong on your local instance? At least the smart button doesn't do anything special just uses a normal action. |
I think the problem was that, I have deleted and re-added the user and there has been no problem. I think it's ready 👍 😄 |
I was using the runboat.. Will reset it and try again. |
@bosd Please check that you aren't using |
@fkantelberg maybe a clarification in the ROADMAP of the module mentioning explicitly runboat there? |
There is a line in the readme Is there a technical reason why the runboat links to http instead of the possible https per default? @bosd |
The file is called ROADMAP.rst, but the section is "Known issues / Roadmap".
@sbidoul can tell you, but if the certificate is self-signed, it's for not having the browser alert and have more questions about that. |
It's not a technical reason, but to avoid the burden of maintaining a trusted wildcard certificate. |
Thanks for the clarifications. I'm used to test stuff on runboat. Did'nt occur to me that is not possible for this module. |
You can just swap to https and confirm the self signed certificate of the runboat to test it. I understand that a wildcard cert can be a burden. I see how I can make it a bit more error prune when not using a secure context and check if I can rephrase the hint in the readme. |
…d. Improve readme documentation about this requirement
The latest patch does some things when the secure browser context isn't available:
Additionally I extended the readme and added it also to the roadmap. I hope this makes it visible enough 😄 |
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.
The latest patch does some things when the secure browser context isn't available:
Hehehe, That's one feature I could test succesfuly 😀
This PR has the |
/ocabot merge nobump |
Hey, thanks for contributing! Proceeding to merge this for you. |
Congratulations, your PR was merged at 23d8df7. Thanks a lot for contributing to OCA. ❤️ |
The migration needed quite a rework because of the JS framework changes. (I hope the next are easier) I tested every functionality during migration but plan to do another round again soon.
There are some minor fixes which were possible to do: