https://issues.apache.org/bugzilla/show_bug.cgi?id=47695
rjohn...@gmu.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #2 from rjohn...@gmu.edu 2009-08-17 16:03:38 PDT ---
Thank you very much! Your suggestion allowed me to generate the correct
structure (replaced "keyInfo.add(encryptedKey)" with
"encryptedDataElement.setKeyInfo(keyInfo)", for anyone using this solution in
the future). I really appreciate the help.
Per your question, what led me to post this as a bug rather than somewhere else
requesting syntactical help was that, from my understanding of the referenced
post, he was indicating that the following is invalid XML and thus XML Security
should never allow it to be generated, nor should it decrypt this structure.
Since .Net failed to decrypt this but Apache did decrypt it, I assumed there
was a problem. I am a novice to all of this, but it did seem logical that
perhaps an error or a different (syntactically legal?) structure should have
been generated in the encrypted document (rather than generating apparently
invalid XML syntax).
EncryptedData
KeyInfo
EncryptedKey
X509Data
I will mark this as Resolved, assuming that my deductions above are incorrect.
Thanks again for the help.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
