Get nameid when element decrypted twice #205
Merged
+84
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After adding tests in our project we figured out that
nameids
could not be decrypted due to a small error. When getting thenameid
andnameid_data
we calldecrypt_element
twice with anetree._Element
. The first time the node is decrypted in place, then the decryption method fail on the second call.Additionally it looks like testing keys are equivalent and tests on the method should not fail because of the keys.
In this PR we add an option to decrypt an element in place or copy it before decryption.