Hi,
I have a WebService Client wsdl that should allow me to PULL an XML file
with embedded PDF attachment from a WebService Server.
Below is the summary of the WSDL:
wsdl:types
xs:schema
attributeFormDefault=unqualified
Hi,
I am not sure how you want to set it up. Where do you expect the
corresponding schema to be specified?
Specified in the message arbitrarily to just validate it own validity
claim or some out of bands schemas are specified for the endpoint to
accept or reject messages?
regards, aki
2015-06-17
Ideally, CXF would just peek at the namespace on the message, pick the schema
corresponding to that namespace from the XML catalog and validate against
that.
Cheers,
Jens
Aki Yoshida-3 wrote
Hi,
I am not sure how you want to set it up. Where do you expect the
corresponding schema to be
Hi,
We don't support BinarySecurityToken SupportingToken policies on their own
in CXF (i.e. without a security binding). The reason being is that they are
largely pointless - you mention wanting an X.509 cert for authentication,
but as there is no signature, there is no proof-of-possession
Could you create JIRAs in WSS4J + CXF and attach the patches there?
Colm.
On Wed, Jun 17, 2015 at 3:44 PM, Freddy Exposito expos...@gmail.com wrote:
Secure Conversation Renew is not working from a .NET client because
ws:Instance is missing in the SecurityContextToken.
Reading into the
Does your service keystore have the private key for bamssouat in it? Or
just the certificate? What is the output of keytool -list -keystore
keystore.jks -v?
Colm.
On Tue, Jun 16, 2015 at 8:26 PM, Vishnu Radhakrishnan vis...@10point1.com
wrote:
I am getting the below error while decrypting
Hi Aki,
The issue stems from the fact that the policy has multiple security
bindings (Symmetric + Transport). CXF 3.0.x checks for Symmetric before
Transport, CXF 3.1.x checks for Transport before Symmetric. Therefore, the
Body is not encrypted in CXF 3.1.x, as encryption is handled by the
This policy does not look right, try removing it:
KeyValueToken IncludeToken= Optional=
Policy /
/KeyValueToken
Colm.
On Fri, Jun 12, 2015 at 1:09 PM, niranjana.murthy
If the ServiceInfo object has a Schema.class property on it that would
represent all the possible schemas, it should work. Thus, if you can build up
a javax.xml.validation.Schema object somehow, you would just need to get that
set on the ServiceInfo. This could be done during startup if
The Jira tickets are: https://issues.apache.org/jira/browse/WSS-542 and
https://issues.apache.org/jira/browse/CXF-6468
Thanks,
Freddy
--
View this message in context:
http://cxf.547215.n5.nabble.com/Issue-with-the-renew-of-SCT-in-Secure-Conversation-tp5758363p5758445.html
Sent from the
When processing a security header, you can determine the key transport
algorithm through WSSecurityEngineResult.TAG_ENCRYPTED_KEY_TRANSPORT_METHOD. Is
there a similar tag that lets you query the new Encryption MGF Algorithm? I
couldn't' find anything in WSSecurityEngineResult. Thanx.
Stephen
11 matches
Mail list logo