You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by Ruwan Linton <ru...@gmail.com> on 2008/04/16 11:22:20 UTC
Re: Timestamp Precision In Milliseconds Configuration At Proxy Level
Hi Rampart folks,
Is this possible (please see the original mail from Alexandre in the
bottom)? if yes can we get this in to the next Rampart release targeting for
the axis2 1.4 release? I know we are very near the deadline :-)
Thanks Alexandre. You could use the JIRA to attach these files, because we
need a license grant from the author of the code for a particular code to go
in to any of the apache projects and JIRA gives the option to state that
with the patch. :-)
Thanks,
Ruwan
On Wed, Apr 16, 2008 at 2:05 PM, alexandre_garino <
alexandre.garino@experian-scorex.mc> wrote:
>
> Hi All,
>
> Do you know if its possible to deal with rampart - at the proxy
> configuration level - to disable milliseconds precision in timestamp
> through
> the Synapse configuration?
>
> Consuming .Net services with milliseconds doesn't work in my specific case
> and I had to apply the patch in attachment to disable the milliseconds.
> This
> patch is far to be perfect, because I change the global configuration
> instead of change the configuration at the message context.
>
> This patch allows to define the timestamp precision settings through the
> ramport config xml fragment enclosed in the policy file:
>
> <ramp:RampartConfig xmlns:ramp="http://ws.apache.org/rampart/policy">
>
> <ramp:timestampPrecisionInMilliseconds>false</ramp:timestampPrecisionInMilliseconds>
> </ramp:RampartConfig>
>
> If one of synapse commiters could push forward to the rampart commiters.
> They could improve and apply the patch to the trunk of rampart and
> consequently enabling such feature in Synapse.
>
> Regards,
> Alexandre
>
>
> http://www.nabble.com/file/p16718940/rampart-timestamp-precision-in-milliseconds.patch
> rampart-timestamp-precision-in-milliseconds.patch<http://www.nabble.com/file/p16718940/rampart-timestamp-precision-in-milliseconds.patchrampart-timestamp-precision-in-milliseconds.patch>
> --
> View this message in context:
> http://www.nabble.com/Timestamp-Precision-In-Milliseconds-Configuration-At-Proxy-Level-tp16718940p16718940.html
> Sent from the Synapse - User mailing list archive at Nabble.com.
>
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Re: Timestamp Precision In Milliseconds Configuration At Proxy
Level
Posted by alexandre_garino <al...@experian-scorex.mc>.
Works fine now. FYI, I built WSS4J, Axis2, Rampart and Synapse from revision
650025.
Regards,
Alexandre
Nunny wrote:
>
> 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
> <al...@experian-scorex.mc> 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.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Timestamp-Precision-In-Milliseconds-Configuration-At-Proxy-Level-tp16718940p16804314.html
Sent from the Synapse - User mailing list archive at Nabble.com.
Re: Timestamp Precision In Milliseconds Configuration At Proxy Level
Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
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
<al...@experian-scorex.mc> 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.
>
>
Re: Timestamp Precision In Milliseconds Configuration At Proxy
Level
Posted by alexandre_garino <al...@experian-scorex.mc>.
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.
Re: Timestamp Precision In Milliseconds Configuration At Proxy
Level
Posted by alexandre_garino <al...@experian-scorex.mc>.
Hi Nandana,
Thanks for your update. I built synapse this morning with your
modifications. I'll give it a try on next monday.
Say thank you to Experian ;o)
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-tp16718940p16763499.html
Sent from the Synapse - User mailing list archive at Nabble.com.
Re: Timestamp Precision In Milliseconds Configuration At Proxy Level
Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
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
Re: Timestamp Precision In Milliseconds Configuration At Proxy Level
Posted by Ruwan Linton <ru...@gmail.com>.
Thanks, Nandana. That will be great.
Ruwan
On Wed, Apr 16, 2008 at 3:10 PM, Nandana Mihindukulasooriya <
nandana.cse@gmail.com> wrote:
> Hi Ruwan/Alexandre.,
>
> > Is this possible (please see the original mail from Alexandre in the
> > bottom)? if yes can we get this in to the next Rampart release targeting
> for
> > the axis2 1.4 release? I know we are very near the deadline :-)
>
> I will review the patch and apply it ASAP. I think we will be able to
> get this in to Rampart 1.4 if everything works fine.
>
> thanks,
> /nandana
>
> >
> > On Wed, Apr 16, 2008 at 2:05 PM, alexandre_garino <
> > alexandre.garino@experian-scorex.mc> wrote:
> >
> > >
> > > Hi All,
> > >
> > > Do you know if its possible to deal with rampart - at the proxy
> > > configuration level - to disable milliseconds precision in timestamp
> > > through
> > > the Synapse configuration?
> > >
> > > Consuming .Net services with milliseconds doesn't work in my specific
> case
> > > and I had to apply the patch in attachment to disable the
> milliseconds.
> > > This
> > > patch is far to be perfect, because I change the global configuration
> > > instead of change the configuration at the message context.
> > >
> > > This patch allows to define the timestamp precision settings through
> the
> > > ramport config xml fragment enclosed in the policy file:
> > >
> > > <ramp:RampartConfig xmlns:ramp="http://ws.apache.org/rampart/policy">
> > >
> > >
> >
> <ramp:timestampPrecisionInMilliseconds>false</ramp:timestampPrecisionInMilliseconds>
> > > </ramp:RampartConfig>
> > >
> > > If one of synapse commiters could push forward to the rampart
> commiters.
> > > They could improve and apply the patch to the trunk of rampart and
> > > consequently enabling such feature in Synapse.
> > >
> > > Regards,
> > > Alexandre
> > >
> > >
> > >
> >
> http://www.nabble.com/file/p16718940/rampart-timestamp-precision-in-milliseconds.patch
> > >
> > rampart-timestamp-precision-in-milliseconds.patch<
> http://www.nabble.com/file/p16718940/rampart-timestamp-precision-in-milliseconds.patchrampart-timestamp-precision-in-milliseconds.patch
> >
> > > --
> > > View this message in context:
> > >
> >
> http://www.nabble.com/Timestamp-Precision-In-Milliseconds-Configuration-At-Proxy-Level-tp16718940p16718940.html
> > > Sent from the Synapse - User mailing list archive at Nabble.com.
> > >
> > >
> >
> >
> > --
> > Ruwan Linton
> > http://www.wso2.org - "Oxygenating the Web Services Platform"
> >
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Re: Timestamp Precision In Milliseconds Configuration At Proxy Level
Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
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
Re: Timestamp Precision In Milliseconds Configuration At Proxy Level
Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
Hi Ruwan/Alexandre.,
> Is this possible (please see the original mail from Alexandre in the
> bottom)? if yes can we get this in to the next Rampart release targeting for
> the axis2 1.4 release? I know we are very near the deadline :-)
I will review the patch and apply it ASAP. I think we will be able to
get this in to Rampart 1.4 if everything works fine.
thanks,
/nandana
>
> On Wed, Apr 16, 2008 at 2:05 PM, alexandre_garino <
> alexandre.garino@experian-scorex.mc> wrote:
>
> >
> > Hi All,
> >
> > Do you know if its possible to deal with rampart - at the proxy
> > configuration level - to disable milliseconds precision in timestamp
> > through
> > the Synapse configuration?
> >
> > Consuming .Net services with milliseconds doesn't work in my specific case
> > and I had to apply the patch in attachment to disable the milliseconds.
> > This
> > patch is far to be perfect, because I change the global configuration
> > instead of change the configuration at the message context.
> >
> > This patch allows to define the timestamp precision settings through the
> > ramport config xml fragment enclosed in the policy file:
> >
> > <ramp:RampartConfig xmlns:ramp="http://ws.apache.org/rampart/policy">
> >
> >
> <ramp:timestampPrecisionInMilliseconds>false</ramp:timestampPrecisionInMilliseconds>
> > </ramp:RampartConfig>
> >
> > If one of synapse commiters could push forward to the rampart commiters.
> > They could improve and apply the patch to the trunk of rampart and
> > consequently enabling such feature in Synapse.
> >
> > Regards,
> > Alexandre
> >
> >
> >
> http://www.nabble.com/file/p16718940/rampart-timestamp-precision-in-milliseconds.patch
> >
> rampart-timestamp-precision-in-milliseconds.patch<http://www.nabble.com/file/p16718940/rampart-timestamp-precision-in-milliseconds.patchrampart-timestamp-precision-in-milliseconds.patch>
> > --
> > View this message in context:
> >
> http://www.nabble.com/Timestamp-Precision-In-Milliseconds-Configuration-At-Proxy-Level-tp16718940p16718940.html
> > Sent from the Synapse - User mailing list archive at Nabble.com.
> >
> >
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"
>
Re: Timestamp Precision In Milliseconds Configuration At Proxy Level
Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
Hi Ruwan/Alexandre.,
> Is this possible (please see the original mail from Alexandre in the
> bottom)? if yes can we get this in to the next Rampart release targeting for
> the axis2 1.4 release? I know we are very near the deadline :-)
I will review the patch and apply it ASAP. I think we will be able to
get this in to Rampart 1.4 if everything works fine.
thanks,
/nandana
>
> On Wed, Apr 16, 2008 at 2:05 PM, alexandre_garino <
> alexandre.garino@experian-scorex.mc> wrote:
>
> >
> > Hi All,
> >
> > Do you know if its possible to deal with rampart - at the proxy
> > configuration level - to disable milliseconds precision in timestamp
> > through
> > the Synapse configuration?
> >
> > Consuming .Net services with milliseconds doesn't work in my specific case
> > and I had to apply the patch in attachment to disable the milliseconds.
> > This
> > patch is far to be perfect, because I change the global configuration
> > instead of change the configuration at the message context.
> >
> > This patch allows to define the timestamp precision settings through the
> > ramport config xml fragment enclosed in the policy file:
> >
> > <ramp:RampartConfig xmlns:ramp="http://ws.apache.org/rampart/policy">
> >
> >
> <ramp:timestampPrecisionInMilliseconds>false</ramp:timestampPrecisionInMilliseconds>
> > </ramp:RampartConfig>
> >
> > If one of synapse commiters could push forward to the rampart commiters.
> > They could improve and apply the patch to the trunk of rampart and
> > consequently enabling such feature in Synapse.
> >
> > Regards,
> > Alexandre
> >
> >
> >
> http://www.nabble.com/file/p16718940/rampart-timestamp-precision-in-milliseconds.patch
> >
> rampart-timestamp-precision-in-milliseconds.patch<http://www.nabble.com/file/p16718940/rampart-timestamp-precision-in-milliseconds.patchrampart-timestamp-precision-in-milliseconds.patch>
> > --
> > View this message in context:
> >
> http://www.nabble.com/Timestamp-Precision-In-Milliseconds-Configuration-At-Proxy-Level-tp16718940p16718940.html
> > Sent from the Synapse - User mailing list archive at Nabble.com.
> >
> >
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"
>