cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From liugang594 Liu <clevers...@gmail.com>
Subject Re: Absolute path of ws-security.signature.crypto doesn't work on REST SAML Support
Date Fri, 02 Aug 2013 09:59:16 GMT
Hi Sergey:

Great news, and thanks for this fix in advance. BTW, whice version does the
fix will be presented?  then I can try on that version.

Thanks.


2013/8/2 Sergey Beryozkin <sberyozkin@gmail.com>

> Hi
>
> On 02/08/13 03:41, liugang594 Liu wrote:
>
>> Hi All:
>>
>> (CXF version: 2.7.7.SNAPSHOT)
>>
>> We are tring to add SAML support on rest service, and the gave attribute
>> ws-security.signature.crypto value is an absolute file path.
>>
>> After deployed this service, we always got an exception, which complains
>> "Caused by: org.apache.ws.security.**WSSecurityException: General
>> security
>> error (Cannot load the resource file:<filePath> )"
>>
>> I traced the code,  in method
>> "org.apache.cxf.rs.security.**common.CryptoLoader.getCrypto(**Message,
>> String,
>> String)" , it always try to load the resource from classpath,
>> unfortunately, it's an absolute path and doesn't exist in current
>> classpath.
>>
>> At present, A way to make it work is providing a customized
>> ResourceResolver on ResourceManager of Bus.
>>
>> I appreciate if there's any other way or configuration to make it work by
>> default?
>>
>>
> Thanks for reporting the issue. I guess typically this was not really
> needed because the stores are available in the container.
> But I understand that you'd like to run it in a non-container mode.
> So please use a custom resolver for now, I'll fix it in the code, and then
> you will be able to drop the resolver code
>
> Thanks, Sergey
>
>  Thanks very much.
>>
>>
>
>


-- 
Thanks
GangLiu
Mail: clevers594@gmail.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message