Hi Alexandre,
Yep, I just went through the Rampart code and found
that when building UsernameTokens, we always use the default WSSConfig
, so the the change that we did didn't affect UT building. It didn't
affect you before as you changed it globally using the default
WSSConfig. I will fix this in Rampart.
thanks,
nandana
On Fri, Apr 18, 2008 at 9:10 PM, alexandre_garino
<[EMAIL PROTECTED]> wrote:
>
> Nandana,
>
> Your patch does not work properly. Here is the request built by Rampart:
>
> <wsse:Security
>
> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
> soapenv:mustUnderstand="1">
> <wsu:Timestamp
>
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
> wsu:Id="Timestamp-6109888">
> <wsu:Created>2008-04-18T15:35:32Z</wsu:Created>
> <wsu:Expires>2008-04-18T15:40:32Z</wsu:Expires>
> </wsu:Timestamp>
> <wsse:UsernameToken
>
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
> wsu:Id="UsernameToken-12333359">
> <wsse:Username>xxxxxxxx</wsse:Username>
> <wsse:Password
>
> Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest";>xxxxxxxx</wsse:Password>
> <wsse:Nonce>xxxxxxxx</wsse:Nonce>
> <wsu:Created>2008-04-18T15:35:32.878Z</wsu:Created>
> </wsse:UsernameToken>
> </wsse:Security>
>
> For Timestamp element it sounds good but the timestamp of Created element
> contains milliseconds.
>
> Regards,
> Alexandre
>
>
>
>
> Nunny wrote:
> >
> > Hi Alexandre,
> > Applied your patch with some changes [1], [2].
> >
> > thanks,
> > /nandana
> >
> > [1] - https://issues.apache.org/jira/browse/RAMPART-152
> > [2] - http://svn.apache.org/viewvc?view=rev&revision=649372
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Timestamp-Precision-In-Milliseconds-Configuration-At-Proxy-Level-tp16718940p16763519.html
>
>
> Sent from the Synapse - User mailing list archive at Nabble.com.
>
>
