I should also add that I moved the private static EncryptedKeyProcessor.getMGFAlgorithm() method into EncryptionUtils, so you can just use this instead with the next release.
Colm. On Mon, Jun 22, 2015 at 10:43 AM, Colm O hEigeartaigh <cohei...@apache.org> wrote: > > No there isn't. I was going to write that what need to do is to retrieve > the DOM Element via WSSecurityEngineResult.TAG_TOKEN_ELEMENT, and then > parse it with code like EncryptedKeyProcessor.getMGFAlgorithm()...however, > it appears we don't store the DOM Element for EncryptedKeys. I have fixed > this for the next release. If you really need the MGF algorithm right now, > I guess you'll need to grab the security header + find the same > EncryptedKey that corresponds to the WSSecurityEngineResult + get the MGF > algorithm from that. > > Colm. > > On Fri, Jun 19, 2015 at 8:23 PM, <stephen.ctr.chapp...@faa.gov> wrote: > >> When processing a security header, you can determine the key transport >> algorithm through >> WSSecurityEngineResult.TAG_ENCRYPTED_KEY_TRANSPORT_METHOD. Is there a >> similar tag that lets you query the new Encryption MGF Algorithm? I >> couldn't' find anything in WSSecurityEngineResult. Thanx. >> >> Stephen W. Chappell >> > > > > -- > Colm O hEigeartaigh > > Talend Community Coder > http://coders.talend.com > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
