Skip to content
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

Get nameid when element decrypted twice #205

Conversation

toopy
Copy link
Contributor

@toopy toopy commented Jun 27, 2017

After adding tests in our project we figured out that nameids could not be decrypted due to a small error. When getting the nameid and nameid_data we call decrypt_element twice with an etree._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.

@toopy toopy force-pushed the get-nameid-when-element-decrypted-twice branch from e2a8455 to 945fc36 Compare June 27, 2017 12:45
@toopy toopy force-pushed the get-nameid-when-element-decrypted-twice branch from 945fc36 to fac4767 Compare June 27, 2017 12:46
@pitbulk
Copy link
Contributor

pitbulk commented Jun 28, 2017

It looks good, let me some days to execute some more tests, merge other PRs and make a new release.

@toopy
Copy link
Contributor Author

toopy commented Jul 27, 2017

UP

@pitbulk
Copy link
Contributor

pitbulk commented Jul 27, 2017

Sorry for the delay, I will test and merge yours PRs today.

@toopy
Copy link
Contributor Author

toopy commented Jul 27, 2017

No emergency, just a small reminder here ;)

@pitbulk pitbulk merged commit 3bda379 into SAML-Toolkits:master Jul 27, 2017
@toopy toopy deleted the get-nameid-when-element-decrypted-twice branch July 31, 2017 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants