Sibling EncryptedKey element is not resolved for decryption.

Description

If the EncryptedKey element is a sibling of the EncryptedData element, the key isn't located by the standard decryption routines.

There are two problems: the wrong version of EncrytedKeyResolver is created in the decrypt method, it's the base class xmltooling version and not the modified opensaml version which knows about sibling elements. But the opensaml version only processes siblings if the Recipient attribute matches a recipient input parameter.

We should fix the EKR class type, modify it to return the first sibling with an absent Recipient. We may also be able to add RetrievalMethod support to the base class version.

Environment

None

Activity

Show:

Scott Cantor December 17, 2010 at 2:39 PM

Closing after release.

Scott Cantor September 6, 2010 at 1:30 PM

Scott Cantor September 6, 2010 at 1:17 PM

Return a sibling key with a missing Recipient attribute:
http://svn.middleware.georgetown.edu/view/cpp-opensaml2?view=rev&revision=574

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Created September 6, 2010 at 12:21 PM
Updated December 17, 2010 at 2:39 PM
Resolved September 6, 2010 at 1:31 PM