I don't see why one couldn't expose the decrypt method. You might want to check out the patch in SHINDIG-811 which might help you load from the resource path.
On Jul 13, 2010, at 10:49 AM, Pablo Graña wrote: > Hi all: > > I'd like to change (in my app) the strategy to get the key used > in BlobCrypterSecurityTokenDecoder. The current way is to read the key from > a file, but I'd like to have it somewhere else. > > My app already has a spring app context, so I'd like to get that key from > there. We created our own SecurityTokenDecoder that also uses the > BlobCrypter. The problem is that the easiest way to go is to invoke > directly BlobCrypterSecurityToken decrypt. But this static operation is > intentionally package access. Can this decision be reviewed? > > Thanks a lot > -- > Pablo Gra\~na > Chief Architect > Globant > Arg Office: +54 (11) 4109 1743 > UK Office: +44 (20) 7043 8269 int 8043 > US Office: +1 (212) 400 7686 int 8043
