> I already read your article (BTW, thank you for writing it!), but haven't > found how to declare custom AlgorithmSuite in WSDL properly. > It is the right way? > <wss:AlgorithmSuite> > <wsp:Policy> > <someNameSpace:customSuite /> > </wsp:Policy> > </wss:AlgorithmSuite>
There is no "proper" way of declaring custom AlgorithmSuites in the WSDL, as it's not supported in the WS-SP specification, as you point out. The example that was linked in the blog just overrides the Basic128 AlgorithmSuite to allow 512 bit asymmetric keys. Your policy statement above looks fine to me though. Colm. On Mon, Jan 23, 2012 at 11:56 AM, Vadim Dmitriev <[email protected]> wrote: > I already read your article (BTW, thank you for writing it!), but haven't > found how to declare custom AlgorithmSuite in WSDL properly. > It is the right way? > <wss:AlgorithmSuite> > <wsp:Policy> > <someNameSpace:customSuite /> > </wsp:Policy> > </wss:AlgorithmSuite> > > WS-SP specification doesn't define how to extend AS, only lists predefined > algorithms, so I'm afraid to use some unspecified controversial approach > which won't be supported anywhere except CXF. > > P.S. > Honestly, I was looking for something like > <AlgorithmSuite id="customSuite"> > <DigestAlgorithm id="..." /> > <EncryptionAlgorithm id="..." /> > </AlgorithmSuite> > This way 3rd parties will have algorithm IDs to use in WS-S header (i.e. > these IDs will be declared in WSDL, not in some external convention). > > --Vadim > > > 23 января 2012, 14:07 от Colm O hEigeartaigh <[email protected]>: >> > - not possible to extend WS-SP declaration to use new AlgorithmSuite >> >> It is possible to do this, see here for more information: >> >> http://coheigea.blogspot.com/2011/09/specifying-custom-algorithmsuite.html >> >> Colm. >> >> -- >> Colm O hEigeartaigh >> >> Talend Community Coder >> http://coders.talend.com >> -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
